Russ Allbery r...@debian.org writes:
For background here, this bug is about permitting the splitting of the
architecture-independent headers for a library into a separate -headers
package rather than requiring (which the current Policy wording implies)
that they be in the usually
On Sat, 2010-06-12 at 13:01 -0700, Russ Allbery wrote:
For background here, this bug is about permitting the splitting of the
architecture-independent headers for a library into a separate -headers
package rather than requiring (which the current Policy wording implies)
that they be in the
For background here, this bug is about permitting the splitting of the
architecture-independent headers for a library into a separate -headers
package rather than requiring (which the current Policy wording implies)
that they be in the usually architecture-dependent -dev package.
Kevin B. McCarty
On Sat, Jun 12, 2010 at 13:01:57 -0700, Russ Allbery wrote:
diff --git a/policy.sgml b/policy.sgml
index 720150d..1e134bb 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -5163,11 +5163,20 @@ Replaces: mail-transport-agent
headingDevelopment files/heading
p
- The
On Wed, Jan 11, 2006 at 11:19:05AM -0500, Kevin B. McCarty wrote:
Could Policy be amended slightly to explicitly permit library source
packages to create a library-headers package containing include files?
I would rather see it modified to not forbid it than add a whole
paragraph to explicitly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Waters wrote:
On Wed, Jan 11, 2006 at 11:19:05AM -0500, Kevin B. McCarty wrote:
Without this or a similar text, it is not clear to me that source
packages creating library-headers binary packages are in compliance
with Policy, which currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: debian-policy
Severity: wishlist
Version: 3.6.2.2
Hi,
Could Policy be amended slightly to explicitly permit library source
packages to create a library-headers package containing include files?
I am thinking that something like the
Kevin B. McCarty [EMAIL PROTECTED] writes:
Could Policy be amended slightly to explicitly permit library source
packages to create a library-headers package containing include files?
I am thinking that something like the following could be added between
the existing first and second
Brian Nelson wrote:
It's not clear to me that splitting out the headers is actually a good
thing (it's very annoying for autobuilders since the corresponding -dev
package won't be installable until the new version has been autobuilt),
so I certainly don't think policy should endorse it.
It
Kevin B. McCarty [EMAIL PROTECTED] writes:
Brian Nelson wrote:
It's not clear to me that splitting out the headers is actually a good
thing (it's very annoying for autobuilders since the corresponding -dev
package won't be installable until the new version has been autobuilt),
so I
Brian Nelson wrote:
Get:1 http://rubeus sid/main libqt3-headers 3:3.3.5-3 [364kB]
Fetched 364kB in 1s (226kB/s)
I wouldn't call 364kB a lot of saved archive space, and you'd be
hard-pressed to find a package with more headers than Qt.
I'm actually working on unofficial packages of Geant 4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin B. McCarty [EMAIL PROTECTED] writes:
Brian Nelson wrote:
It's not clear to me that splitting out the headers is actually a good
thing (it's very annoying for autobuilders since the corresponding -dev
package won't be installable until the
On Wed, Jan 11, 2006 at 01:04:44PM -0500, Kevin B. McCarty wrote:
benjo (sid)[126]:~% ls -l src/GEANT4/geant4-headers_4.8.0-1_all.deb
-rw-r--r-- 1 kmccarty kmccarty 1300680 2006-01-11 11:58
src/GEANT4/geant4-headers_4.8.0-1_all.deb
but I guess even 11 * (1.3 MB) isn't so much compared to the
Bill Allombert wrote:
On Wed, Jan 11, 2006 at 01:04:44PM -0500, Kevin B. McCarty wrote:
benjo (sid)[126]:~% ls -l src/GEANT4/geant4-headers_4.8.0-1_all.deb
-rw-r--r-- 1 kmccarty kmccarty 1300680 2006-01-11 11:58
src/GEANT4/geant4-headers_4.8.0-1_all.deb
but I guess even 11 * (1.3 MB) isn't so
14 matches
Mail list logo
