On Mon, Apr 07, 2003 at 08:59:25PM +0200, Josip Rodin wrote:
> On Mon, Apr 07, 2003 at 08:03:18PM +0200, Bill Allombert wrote:
> > > > Firstly, a test to see if something is a makefile can be as simple as
> > > > reading the first line of the file -- does it contain #!/usr/bin/make
> > > > -f (as p
On Mon, Apr 07, 2003 at 08:03:18PM +0200, Bill Allombert wrote:
> > > Firstly, a test to see if something is a makefile can be as simple as
> > > reading the first line of the file -- does it contain #!/usr/bin/make
> > > -f (as policy dictates in 5.2)
> >
> > Wrong. Debian policy is just that, De
Package: dpkg-dev
Version: 1.10.9
Followup-For: Bug #148932
Wichert wrote:
> Previously Duncan Findlay wrote:
> > Firstly, a test to see if something is a makefile can be as simple as
> > reading the first line of the file -- does it contain #!/usr/bin/make
> > -f (as policy dictates in 5.2)
>
>
Wichert Akkerman wrote:
> Previously Peter S Galbraith wrote:
> > It would be nice if `dpkg-buildpackage -B` first tried the build-arch
> > target of debian/rules and only revert to the more lengthy and wasteful
> > build target if build-arch weren't present.
>
> Issue is how to detect if debian
Previously Peter S Galbraith wrote:
> It would be nice if `dpkg-buildpackage -B` first tried the build-arch
> target of debian/rules and only revert to the more lengthy and wasteful
> build target if build-arch weren't present.
Issue is how to detect if debian/rules does not support build-arch.
D
Package: dpkg-dev
Version: 1.9.20
Severity: wishlist
I was told today that autobuilders use `dpkg-buildpackage -uc -us -B
-r` to build packages for the various arches. Therefore
a lot of CPU cycle are wasted building arch-independent stuff that will
never be used (since the _all package isn't pre
6 matches
Mail list logo
