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

Bug#218893: Proposal: debian/rules.version file [Fix for the build-arch problem]

On Fri, Nov 14, 2003 at 01:49:19PM +0100, Bill Allombert wrote:
> > > I appreciate your efforts, but i'm sorry: i still have not seen a reply to
> > > last mail from Branden:
> > > Message-ID: <20031112000742.GD30281@deadbeast.net>
> > > References: <20031110053453.GU27445@deadbeast.net>
> > 
> > Please could you provide references in the form of
> > http://lists.debian.org/... so that we can track these down?
> Here it is:
> http://lists.debian.org/debian-policy/2003/debian-policy-200311/msg00092.html
> Note that http://lists.debian.org autmomatically add link to messages
> matching Message-ID.

How?  I haven't figured out how to search by Message-ID.

> However, Branden question belong more to debian-dpkg than here.

In response to Branden's question (does debian/control already have to
exist when the package is unpacked), I would suggest the following:

Before debian/rules build* is run, one has to check the
build-dependencies.  So at this point, at least the source section of
debian/control must exist.  And since this field (whatever form it
eventually takes) would exist in the source section of debian/control,
and would not be needed until after the build-dependencies are
checked, there should be no problem.

And then again, we can always use debian/interfaces or
debian/rules.targets or something similar instead....



        Julian Gilbey, website: http://www.polya.uklinux.net/
   Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/
     Visit http://www.thehungersite.com/ to help feed the hungry

Reply to: