hierarchy in setup (category stuff)

Christopher Faylor cgf@redhat.com
Fri Jun 29 17:56:00 GMT 2001

On Sat, Jun 30, 2001 at 10:51:44AM +1000, Robert Collins wrote:
>> Either way, there would still be problems.  I think that they are mainly
>> of Michael's white space fixes.
>> I sometimes wish that we had a C/C++ aware version of patch.
>My .2c: update your CVS server. I have much much less problems with merges
>with the sourceforge CVS server.

I was using patch, actually.  I don't know how CVS would affect this.

But, I do want to update the server.  It's been patched locally, so I'm really
reluctant to tackle this but I really really should do this.

>> >> Robert, if you are still interested, then I think that this is
>definitely the
>> >> way to go.  If you have something worth checking in, then please do so.
>I'll draw up change log stuff and send something to cygwin-patches... or did
>you want me to hit CVS directly?

Go ahead and check it in.  We can tweak it later.

>>I'm thinking that we should just nuke the "latest" and "contrib"
>>directories and create directories based on the name of the categories.
>I don't think we even need separate directories - they don't do much
>once the package system manages the view :].

I was just thinking of using the directories as an organizational method
for the packages on sourceware.  The alternative is to somehow get the
information into the setup.hint file there or to add some other file to
the directory.  That's a lot of work and it's error-prone.  I can easily
foresee erroneously having a Development and a Devlopment (misspelled)
category if we do this on a per-package basis.

As far as the layout on the user's side, I don't really care, except
that we could almost forgo setup.ini completely and just rely on the
directory layout for "Install From Current Directory".

The next thing we have to do is add descriptions.  That will involve
another chooser change.


More information about the Cygwin-developers mailing list