On Friday 03 October 2008 22:03:52 Lukas Oboril wrote: > On Fri, Oct 3, 2008 at 4:38 PM, Adriaan de Groot <groot at kde.org> wrote: > > - Write SPEC files so that *just* pkgtool is enough > > - Be flexible in where sources come from > > - Allow rolled-from-Dude tarballs > > - Allow externally hosted (say the upstream tarballs) as well > > - Check the accuracy of license statements in passing > > - Learn to use Mercurial as well > > Do you want to use mercurial ?
Yes, but that is a whim: I wanted to use some DVCS, even if it's not sensible to do so on my own. I'm just listing what motivated me to put some effort into this and what my goals were. Because one goal was to learn mercurial, I used mercurial. > Do you want to use SPEC instead of PSPC ? Yes. PSPC is *almost* a SPEC file and is transformed by Respect.pl into a SPEC file. Respect also does some other stuff related to the structure of the Dude repository. I wanted to take out two steps which I find annoying and counter- productive: - Having to run Respect.pl to generate the spec files. All it really does is insert the boilerplate code, but that is what %include can be used for (remember, when I wrote Respect.pl my total knowledge of spec files was based on copying what you, Luc, were doing). There is really no point in doing that. The SPEC file format is fully capable of doing that kind of boilerplate handling itself. - Not being able to use a combination of pristine upstream sources (e.g. tarballs hosted at sourceforge) + our Solaris/ scripts and patches for each package. That is, I feel that needing a Dude checkout to build the packages is not good for general use. It is excellent for us who *write* the packages because we want to have the source available for all three of us (or five, but there's not many people in this category) and work together on the patches, but at some point you want to be able to hand a regular (-ish) user a bunch of files and say "press this button and things happen automatically." > > My intentions at this point are vague. I'd like to put this stuff up > > somewhere, but I see it as something separate from the work done in Dude. > > It might be good for public perception (for such public as there is) to > > have it in a repo associated with the KDE project on opensolaris.org. > > Do you plan use mercurial on opensolaris.org ? Yes, if I can figure out how to get at it. See other message. [ade]
