Re: [Audacity-devel] id3tag issue with audacity-1.2 cvs
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Dave F. <dav...@co...> - 2003-10-01 09:03:42
|
On Wednesday 01 October 2003 12:09 am, Joshua Haberman wrote: <snip> > > In my opinion, the real problem is that the GNU autotools do NOT > > provide a way to create a "release" package that will never, under any > > circumstances, run autoconf or automake, or any tool that isn't in > > the directory itself. There should just be a flag somewhere that you > > can set that says "release mode" - and to edit the configuration > > scripts all you'd need to do is remove the flag. But for the 99% of > > us that just want to download and use the package, but making use of > > CVS for convenience, that would save us loads of trouble. > > I am not arguing that such a flag would not be useful, but I think that > perhaps another solution would be not to put generated files such as > 'configure' in CVS. You get thousands of lines of meaningless diffs all > the time and I think it is likely that the problems you are describing > are also a symptom. > > Many many projects do not keep these automatically generated autotools > files in CVS, but instead have a ./autogen.sh script that calls the > appropriate autotools in sequence. I am not completely sure this would > solve the problem you are describing, but I think it's a least something > worth investigating and considering. When Dominic posted, I went looking for documentation I had previously read, but couldn't find it. Anyway, what I remember reading is that you're not supposed to distribute configure (ideally), but everyone does. Reading your post, though, I remember what it is I read, and I'm pretty sure it's in the automake manual. You're supposed to generate configure right before releasing. I found what I read, finally, and here's a link: http://sources.redhat.com/automake/automake.html#CVS It appears that I wasn't totally right in my memory of what I read. :) But read the question and long answer, it looks like if you use automake completely (which audacity does not) then Dominic's problem does get solved. Personally, I've done a small amount of work with Makefile.ams, and I'm willing to offer some time to change the build system over to it. But I seem to remember that you guys made a conscious decision not to use automake in that fashion. In any case, if you're interested, I've recently gotten fairly acquainted with Audacity's build system and I'd be happy to take care of this. Dave > Josh > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel -- "Refuse to be denied, refuse to compromise "Your ideology always a lie "Imperialistic, colonialistic "Bandwagon patriot wake up to this" -Anthrax, "Refuse to be denied" |