[Chicken-janitors] Re: #91: reorganize egg repository to cut down working copy size

[Chicken Trac]

#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  |  
------------------------+---------------------------------------------------

Old description:

> Checking out the complete egg repository requires a considerable amount
> of disk space. During a discussion with ashinn, sjamaan, iraikov,
> zbigniew and mario, we came to the conclusion that it would be a win if
> one could merely check out the development sources, not the tagged
> copies. One possible new layout would be:
>
> {{{
> stable/release/4/spiffy.scm
> stable/release/4/spiffy.setup
> ...
> dev/release/4/spiffy/1.0
> dev/release/4/spiffy/1.1
> ...
> }}}
>
> Things to keep in mind:
>
>  * the henrietta instances have to be updated to export from the correct
> URLs
>  * the restructuring will invalidate all working copies and likely make
> it very difficult to check in uncommitted changes, so the change should
> be announced early enough and be done during of period in which no other
> repo access can take place

New description:

 Checking out the complete egg repository requires a considerable amount of
 disk space. During a discussion with ashinn, sjamaan, iraikov, zbigniew
 and mario, we came to the conclusion that it would be a win if one could
 merely check out the development sources, not the tagged copies. One
 possible new layout would be:

 {{{
 stable/release/4/spiffy/spiffy.scm
 stable/release/4/spuffy/spiffy.setup
 ...
 dev/release/4/spiffy/1.0
 dev/release/4/spiffy/1.1
 ...
 }}}

 Things to keep in mind:

  * the henrietta instances have to be updated to export from the correct
 URLs
  * the restructuring will invalidate all working copies and likely make it
 very difficult to check in uncommitted changes, so the change should be
 announced early enough and be done during of period in which no other repo
 access can take place

--

Comment(by felix):

 Replying to [comment:3 tonysidaway]:
 >
 > 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

 Yes, that's right. Sorry.

 >
 > 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.

 Quite right - I incorreclty omitted the eggname.

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