On Thu, 10 Sep 2009 09:50:04 +1000 Simon Horman <ho...@verge.net.au> said:
> On Wed, Sep 09, 2009 at 09:30:24AM +0200, Albin Tonnerre wrote: > > On Wed, 09 Sep 2009 09:24 +1000, Simon Horman wrote : > > > Is the following appropriate? > > > > > > ----------------------------------------------------------------------------- > > > > > > Subject: Add autogen.sh to dist tarball > > > > > > autogen.sh is used by the debian packaging so it seems > > > appropriate to include it in the dist tarball > > > > Either you're packaging from SVN and therefore don't need it to be part of > > the dist tarball, or you're packaging from the snapshots at > > download.enlightenment.org (or snapshots you generated) and then your > > packaging should be fixed to use directly ./configure instead of > > configure.sh. Is there an actual use case I'm missing, for which this > > change would be required? > > Thanks for filling me in on the expected usage. actually. alibin is wrong (sorry!) autogen's do get packaged. look at existing efl. we put it in so if u get a tarball u CAN easily modify the configure.ac, Makefile.am's etc. and re-generate the autofoo. the script will be there with all the magic. not everyone will want or need to do this from a tarball dist - but it dos happen. people patching packages are often the ones using it. so it's not valid. it's an omission in the esmart build foo. :) (even if albin was right - eet, evas, elementary, edje, ... etc. all include autogen.sh in their EXTRA_DIST, so it'd go in for consistency sake. it's goo to have everything in svn have consistent autofoo files and work the same way. it makes everything hav the same bug o everything is right. not some things buggy, some not, in terms of autofoo usage/structure, so if u do find a bug/issue - u can know that fixing it everywhere else is trivial) > I was thinking of the case where you want to test what is > in SVN by: > > 1) creating a tarball > 2) building a debian package from that tarball after unpacking is > and manually copying over the debian/ directory from SVN. > > But if thats not valid, I'll stop doing it. > > When you say fixed to use ./configure directly, when and how does that occur? > I agree that calling ./configure is preferable when building Debian packages. > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
