Christopher Faylor <[EMAIL PROTECTED]> writes: > On Mon, Jul 08, 2002 at 10:39:12AM -0400, Charles Wilson wrote: >>I'll reiterate Chris' comment, here: one tool, one job. Perhaps the >>"let's make a cross build env" part could be a *separate* script, that >>USES mknetrel. > > Actually, the mknetrel CVS repository has a couple of small tools: > "bump" and "pimport". bump changes the version number of a source > directory. pimport takes a tar file and puts it in the src directory, > correctly named. > > pimport might be a good place to put a "grab stuff from the ftp site" > logic.
Ok. I didn't look close enough at the resulting packages. As it turns out, there's another difference with the cygwin-cross tools: mknetrel uses packaging method1, where the cross-tools use method2. Actually, I had the impression that method1 was more or less deprecated, and that we were moving to method2? For packaging method2, it makes a lot of sense for `the packaging tool' to untar the (pristine) source itself, to assure the diff that gets generated is correct. Anyway, we'll see about that later. First, the mknetrel patches. Greetings, Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
