FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 06-17-2012, 08:34 PM
Vincent Danjean
 
Default Bug#677474: Substvars for Build-Depends in the .dsc file

Le 17/06/2012 14:00, Joachim Breitner a écrit :
> Hi,
>
> it seems that my idea is not well received; point taken, and I do like
> the alternative about debian/rules creating debian/control in the clean
> target.

Modifying debian/control within the clean target of debian/rules would
lead to lots of problems already cited (build-depends must be known and
correct just after downloading the sources).

However, you can implement a 'rules' called in the clean target that
check (and perhaps fails) if the current build-depends are wrong (and
if it proposes the good one, the fix will be quick when building the
package initially). Something similar to what is done for symbols for
shared libraries...

Regards,
Vincent

> Nevertheless :-)

--
Vincent Danjean GPG key ID 0x9D025E87 vdanjean@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FDE3F62.9040406@free.fr">http://lists.debian.org/4FDE3F62.9040406@free.fr
 
Old 06-18-2012, 12:10 PM
Roger Leigh
 
Default Bug#677474: Substvars for Build-Depends in the .dsc file

On Sun, Jun 17, 2012 at 01:39:05PM +0200, Goswin von Brederlow wrote:
> I think that the sources-subvars target must function without any
> Build-Depends-(Indep) installed because otherwise:

Just as an aside, we now have Build-Depends-Arch in addition to
Build-Depends-Indep. This means that Build-Depends can be
restricted to the common subset needed for packing sources but
not those needed for arch-all or arch-any building.


Regards,
Roger

--
.'`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120618121014.GE30022@codelibre.net">http://lists.debian.org/20120618121014.GE30022@codelibre.net
 
Old 06-21-2012, 07:28 AM
Wouter Verhelst
 
Default Bug#677474: Substvars for Build-Depends in the .dsc file

On Thu, Jun 14, 2012 at 11:04:00AM +0200, Joachim Breitner wrote:
> Hi Bernd,
>
> Am Donnerstag, den 14.06.2012, 10:32 +0200 schrieb Bernd Zeimetz:
> > > I would like to see more flexibility in dpkg-source as to where the
> > > effective build depends come from. My use case are (as you might guess)
> > > Haskell packages. If you look at
> > > http://ftp.de.debian.org/debian/pool/main/h/haskell-yesod/haskell-yesod_1.0.1.6-1.dsc
> > > you see it has a very long list of build dependencies. If you’d compare
> > > that to
> > > http://hackage.haskell.org/packages/archive/yesod/1.0.1.6/yesod.cabal
> > > you’d see that the process of creating the build dependencies is a
> > > mostly mechanical process and doing that manually is a waste of human
> > > developer time and a source for mistakes (which lead to FTBFSes and
> > > hence more waste in buildd and buildd admin time).
> >
> > Other peopel solve this by having a debian/control.in file and having
> > - a debian/control target in debian/rules
> > - having the clean target depend on debian/control.
> >
> > I don't think that your case is special enough to add yet an extra
> > option to dpkg-source. I have two packages where I'm changing much more
> > than the build-dependencies automatically, for example.
>
> I am aware of approaches using debian/control.in, but I was under the
> impression that during the build, debian/control must not be changed and
> hence this always requires manual interaction.

Yes, and the reason for this is that we don't want accidental
build-depends changes by builds on buildd hosts. Your proposed change
would violate that.

It's fine to use the control.in approach provided it doesn't get done in
an automatic build. Just make sure you have a separate debian/rules
target which regenerates debian/control when called manually and
explicitly, and you should be fine.

Then building your package's maintainer upload just involves
"debian/rules <build-control-target>" followed by a dpkg-buildpackage as
usual.

--
The volume of a pizza of thickness a and radius z can be described by
the following formula:

pi zz a


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120621072845.GL21287@grep.be">http://lists.debian.org/20120621072845.GL21287@grep.be
 
Old 06-21-2012, 07:37 AM
Wouter Verhelst
 
Default Bug#677474: Substvars for Build-Depends in the .dsc file

On Sun, Jun 17, 2012 at 02:00:04PM +0200, Joachim Breitner wrote:
> Hi,
>
> it seems that my idea is not well received; point taken, and I do like
> the alternative about debian/rules creating debian/control in the clean
> target.

Do. Not. Do. That.

Ever.

if you do, you risk all kinds of problems, like binNMUs having broken
control files, your package FTBFSing because the script used to generate
the control file no longer functions, and similar things.

Building debian/control in an automated fashion is fine, but it must not
be done as part of any regular "dpkg-buildpackage" call. This includes
-S, -b, and -B builds (the latter is used by buildd, fwiw).

--
The volume of a pizza of thickness a and radius z can be described by
the following formula:

pi zz a
 
Old 06-21-2012, 03:08 PM
Ben Hutchings
 
Default Bug#677474: Substvars for Build-Depends in the .dsc file

On Thu, Jun 21, 2012 at 09:37:03AM +0200, Wouter Verhelst wrote:
> On Sun, Jun 17, 2012 at 02:00:04PM +0200, Joachim Breitner wrote:
> > Hi,
> >
> > it seems that my idea is not well received; point taken, and I do like
> > the alternative about debian/rules creating debian/control in the clean
> > target.
>
> Do. Not. Do. That.
>
> Ever.
>
> if you do, you risk all kinds of problems, like binNMUs having broken
> control files, your package FTBFSing because the script used to generate
> the control file no longer functions, and similar things.
>
> Building debian/control in an automated fashion is fine, but it must not
> be done as part of any regular "dpkg-buildpackage" call. This includes
> -S, -b, and -B builds (the latter is used by buildd, fwiw).

Well, you can update automatically, but you have to make the target
fail if it actually changes the control file. (This is roughly what
'linux' and closely associated packages do.)

Ben.

--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120621150838.GP2753@decadent.org.uk">http://lists.debian.org/20120621150838.GP2753@decadent.org.uk
 

Thread Tools




All times are GMT. The time now is 09:47 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org