Joey Hess writes (Re: Debian Policy 3.9.4.0 released):
That would include large numbers of haskell libraries and binaries that
statically link other haskell libraries. Even though most such
libraries actually have no source license requirements.
The requirement to ship the source
Russ Allbery writes (Re: Debian Policy 3.9.4.0 released):
Well, I'll use that version once we get the multiarch changes in for sure.
:)
4.x surely :-).
Ian.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Russ Allbery wrote:
7.8
New `Built-Using' field, which must be used to document the
source packages for any binaries that are incorporated into this
package at build time. This is used to ensure that the archive
meets license requirements for
On Wed, 19 Sep 2012, Joey Hess wrote:
Russ Allbery wrote:
7.8
New `Built-Using' field, which must be used to document the
source packages for any binaries that are incorporated into this
package at build time. This is used to ensure that the archive
Hi,
On Wed, Sep 19, 2012 at 10:01:39AM -0700, Don Armstrong wrote:
On Wed, 19 Sep 2012, Joey Hess wrote:
Russ Allbery wrote:
7.8
New `Built-Using' field, which must be used to document the
source packages for any binaries that are incorporated into this
Joey Hess jo...@debian.org writes:
It seems that this was intended to apply to standalone binaries embedded
into things like d-i initrds (which already use it), but as it's written
it seems to apply to static linking of libraries as well.
That would include large numbers of haskell libraries
Ian Jackson ijack...@chiark.greenend.org.uk writes:
Russ Allbery writes (Re: Debian Policy 3.9.4.0 released):
Well, I'll use that version once we get the multiarch changes in for
sure. :)
4.x surely :-).
Hm, I was hanging on to the 4.x version for rewriting the thing in DocBook
Don Armstrong wrote:
This sort of sounds like Built-Using: only needs to contain things
which the package doesn't already Depends: (or perhaps even
Recommends:) on. [Which would resolve the archive licensing
requirements.]
To to usable to ensure GPL compliance, Built-Using needs to specify
Joey Hess jo...@debian.org writes:
Don Armstrong wrote:
This sort of sounds like Built-Using: only needs to contain things
which the package doesn't already Depends: (or perhaps even
Recommends:) on. [Which would resolve the archive licensing
requirements.]
To to usable to ensure GPL
Quoting Russ Allbery (r...@debian.org):
I've just uploaded Debian Policy 3.9.4.0, which includes the Technical
Committee decision to make build-arch and build-indep mandatory targets
(but not for wheezy; see below), a substantial rewrite of the section on
shared library handling, and other
Christian PERRIER bubu...@debian.org writes:
Thanks again and again for the great work maintaining the policy (and
lintian as well).
Given the quite important change of making build-{arch,indep} targets
mandatory, wouldn't have been better to use something like 3.10.1 or
anything clearly
11 matches
Mail list logo
