chicken-janitors
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-janitors] Re: #91: reorganize egg repository to cut down workin


From: Chicken Trac
Subject: [Chicken-janitors] Re: #91: reorganize egg repository to cut down working copy size
Date: Wed, 28 Oct 2009 15:04:06 -0000

#91: reorganize egg repository to cut down working copy size
------------------------+---------------------------------------------------
 Reporter:  felix       |       Owner:       
     Type:  task        |      Status:  new  
 Priority:  major       |   Milestone:  4.3.0
Component:  extensions  |     Version:  4.2.x
 Keywords:  repository  |  
------------------------+---------------------------------------------------

Comment(by tonysidaway):

 Although this would probably impact me as any time I'm developing Chicken
 software I'm likely to be working on eggs continually, I welcome the
 proposal and don't mind the minor inconvenience that might be caused by
 having to adapt a set of uncommitted changes to the new directory
 structure.  After the transition one would just have to repeat the
 checkout for the new structure and then merge in the changed files, copy
 the release to the new dev branch, and commit in both branches. Have I
 missed anything out?

 Being able to check out development copies of many eggs easily without a
 high cost in diskspace would be a very worthwhile change, and one
 especially evident to me as I'm working on a 10GB Ubuntu installation on a
 laptop most of the time.

 Felix, in your opening entry, you refer to the following pattern for the
 stable branch:

 stable/release/4/spiffy.scm
 stable/release/4/spiffy.setup

 Do you mean the following?

 stable/release/4/spiffy/spiffy.scm
 stable/release/4/spiffy/spiffy.setup

 If you do the former I think it implies that all source files from all
 eggs would share the same directory and hence the same file namespace,
 which would definitely not work without renaming a lot of source files
 (doc.scm, tests/run.scm, etc). It would also make it difficult to check
 out the stable branch of a single egg.

-- 
Ticket URL: <http://www.irp.oist.jp/trac/chicken/ticket/91#comment:3>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]