discuss-gnustep
[Top][All Lists]
Advanced

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

Re: help for packagers (was: Re: FOSDEM Aftermath - the Hotel / Notes fr


From: Lars Sonchocky-Helldorf
Subject: Re: help for packagers (was: Re: FOSDEM Aftermath - the Hotel / Notes from preparing and giving my talk)
Date: Thu, 26 Feb 2009 02:00:18 +0100


Am 25.02.2009 um 10:14 schrieb Nicola Pero:

my proposal:

- as a first measure we should include a PACKAGERS.readme file into each core package (make, base, gui and back) which: * contains a pointer to gnustep-packagers@gna.org and discuss- gnustep@gnu.org * contains a pointer to our bug reporting system (with the hint to report bugs "upstream")
* explains some basic concepts about the respective package
* gives some helpful hints
* what else?

I agree. In fact in December, I added a README.Packaging to gnustep-make (under Documentation), which should include a summary of most of the information needed to package GNUstep stuff. :-)

Great! I didn't know that (because I did not look there - but will others look there?)


(feel free to suggest improvements to that file!)

I will read it the next days and post my comments


After your comments, I added to the file a reference to the mailing list. I don't think it's a good idea to have a separate mailing list for packagers though, since nobody would be subscribed to it so it's unlikely that help request will get answered. Is it OK to
tell people to ask for help at help-gnustep@gnu.org ?

Maybe the file should go top-level so it's more prominent ?

I thought about that too, but then again all packages (make, base, gui and back) are released as self contained tar balls here:

http://wwwmain.gnustep.org/resources/downloads.php?site=ftp%3A%2F% 2Fftp.gnustep.org%2Fpub%2Fgnustep%2F

and some folks will even package only some of them for their distribution. The readme files should be in there.


Thanks


regards,

        Lars




reply via email to

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