This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Setup/prev/curr/test/metapackages/another screen/etc


Christopher Faylor <cygwin-apps@cygwin.com> writes:

> I really wish we had never even come up with the concept of
> prev/curr/test.  Maybe the prev release should be a completely separate
> release, ditto test.  You choose it early on in the setup process and
> have setup.exe select from.

I'm all for this.  Of course, the separation can be implemented in
different ways.

> test/latest
> test/contrib
>
> curr/latest
> curr/contrib

Why not keep the directory structure simple, and have eg,
setup-test.ini, setup-curr.ini, setup-prev.ini.  That way no tarballs
need to be moved/copied from test to curr after found stable.  Also,
you'll want test to be afull release (ie, include 'curr' packages for
packages that don't have a test version).

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]