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

Re: DRAFT: Fixing the architecture query options of dpkg.



On Fri, 8 Jan 1999, Marcus Brinkmann wrote:

> 
> So, dpkg-buildpackage would call "make debian/whatever" with following
> environments:

Minor glitch - currently, policy doesn't mandate that debian/rules be a
make script (and this is probably a good thing).  So, dpkg-buildpackage
should simply execute debian/rules.

> The only drawback I can see: If you do cross compilation, you can't easily
> run "debian/rules target" and expect it to work. You'd need to set the
> variables correctly. However, this is a small price and does only affect
> cross compilation. Currently, cross compilation is not supported at all
> (without major hacks and dpkg-cross), so this is not a big deal. (This is a
> direct consequence from the fact that we don't have a debian/configure,
> similar to GNU configure. GNU configure does not have the problem, because
> it builds the Makefiles before using them. In our case, a default of native
> compilation is hard coded in the rules files, for backward compatibility).

My gut instincts tell me that encouraging people to use dpkg-buildpackage
is *good* since this means we can incorporate future ideas like this one
directly there.   We should simply make dpkg-buildpackage more flexible
(so that, for example, in the event you don't want a whole build, you can
specify a target - if we don't already have this functionality).

Jules


/----------------+-------------------------------+---------------------\
|  Jelibean aka  | jules@jellybean.co.uk         |  6 Evelyn Rd	       |
|  Jules aka     | jules@debian.org              |  Richmond, Surrey   |
|  Julian Bean   | jmlb2@hermes.cam.ac.uk        |  TW9 2TF *UK*       |
+----------------+-------------------------------+---------------------+
|  War doesn't demonstrate who's right... just who's left.             |
|  When privacy is outlawed... only the outlaws have privacy.          |
\----------------------------------------------------------------------/


Reply to: