On ke, 2010-09-15 at 09:45 +0100, Lars Wirzenius wrote:
Good point about debian/watch.
The simplest proposal right now is to make the Source field free-form
text, and since I like simplicity, I support this. More detailed
specification for documenting mechanical rules of transformations
On ti, 2010-09-14 at 17:35 -0700, Russ Allbery wrote:
Jonas Smedegaard d...@jones.dk writes:
Makes sense to me.
Let's define only a single free-form field in the header section now.
I suggest it then be a field specifically for notes regarding source not
being pristine in the sense
On Tue, Sep 14, 2010 at 12:07:21AM +0100, Stuart Prescott wrote:
- if the transformation can be expressed as a script, use
debian/rules get-orig-source
Since the purpose of the get-orig-source target seems to have become
unclear over time, this doesn't sound like a good plan to me. The
On ma, 2010-09-13 at 14:54 -0700, Russ Allbery wrote:
There should still be an explanation in debian/copyright of what that
script does, since that's the Policy-required location for specifying
where the upstream source came from.
Oh, I thought only devref was requiring that to be in
On ti, 2010-09-14 at 00:07 +0100, Stuart Prescott wrote:
Personally, I'd like a nice machine-readable list of files/dirs/globs that
should be removed from the tarball. I'd like it to be kept in a canonical
location in the source tarball (debian/copyright, perhaps?)
This all sounds good, with
On Tue, Sep 14, 2010 at 12:57:28PM +0100, Lars Wirzenius wrote:
On ti, 2010-09-14 at 00:07 +0100, Stuart Prescott wrote:
Personally, I'd like a nice machine-readable list of files/dirs/globs
that should be removed from the tarball. I'd like it to be kept in a
canonical location in the source
Jonas Smedegaard d...@jones.dk writes:
Makes sense to me.
Let's define only a single free-form field in the header section now.
I suggest it then be a field specifically for notes regarding source not
being pristine in the sense that the form as redistributed by Debian is
different from
On Tue, Sep 14, 2010 at 05:35:12PM -0700, Russ Allbery wrote:
Jonas Smedegaard d...@jones.dk writes:
Makes sense to me.
Let's define only a single free-form field in the header section now.
I suggest it then be a field specifically for notes regarding source
not being pristine in the
Jonas Smedegaard d...@jones.dk writes:
To me, Source: contains origins. Makes sense to me for that field to
be mandatory and only contain URLs.
I would like an optional field indicating that our redistribute as the
source (rather than our overlay part in the form of either a patch
or (with
On Tue, Sep 14, 2010 at 06:23:12PM -0700, Russ Allbery wrote:
Jonas Smedegaard d...@jones.dk writes:
To me, Source: contains origins. Makes sense to me for that field
to be mandatory and only contain URLs.
I would like an optional field indicating that our redistribute as
the source
Jonas Smedegaard d...@jones.dk writes:
On Tue, Sep 14, 2010 at 06:23:12PM -0700, Russ Allbery wrote:
It seems like overkill to me, but I guess I don't really care. But if
the source is only URLs, then for some of my packages I either need to
omit it or duplicate Homepage, since I don't use
On Tue, Sep 14, 2010 at 07:17:59PM -0700, Russ Allbery wrote:
Jonas Smedegaard d...@jones.dk writes:
On Tue, Sep 14, 2010 at 06:23:12PM -0700, Russ Allbery wrote:
It seems like overkill to me, but I guess I don't really care. But
if the source is only URLs, then for some of my packages I
Jonas Smedegaard d...@jones.dk writes:
I am fine with Source field permitting free-form text, as long as the
scope of that field is limited to covering the question where did
upstream release the source that was the main basis for this package?
I think where we're disagreeing is that I don't
From the DEP5 wiki page:
Dev-ref §6.7.8.2 recommends that if you have to repackage the original
source, that the transformations that are performed be recorded in
debian/copyright. While there was recently some discussion on d-devel
about whether repackaging just to remove
Le Mon, Sep 13, 2010 at 03:03:00PM +0100, Lars Wirzenius a écrit :
My opinions:
- if the transformation can be expressed as a script, use debian/rules
get-orig-source
- otherwise, debian/README.Source seems like a better place to document
this than debian/copyright, since it has other
On Mon, Sep 13, 2010 at 03:03:00PM +0100, Lars Wirzenius wrote:
From the DEP5 wiki page:
Dev-ref §6.7.8.2 recommends that if you have to repackage the original
source, that the transformations that are performed be recorded in
debian/copyright. While there was recently some discussion on
On ma, 2010-09-13 at 16:58 +0200, Jonas Smedegaard wrote:
It makes good sense to me that we (continue to) track stripped files at
the same place as distributed files.
On the other hand, I don't see the point of using debian/copyright to
document copyright information of files that are not part
* Lars Wirzenius l...@liw.fi [100913 19:05]:
On ma, 2010-09-13 at 16:58 +0200, Jonas Smedegaard wrote:
It makes good sense to me that we (continue to) track stripped files at
the same place as distributed files.
On the other hand, I don't see the point of using debian/copyright to
On Mon, Sep 13, 2010 at 06:05:12PM +0100, Lars Wirzenius wrote:
On ma, 2010-09-13 at 16:58 +0200, Jonas Smedegaard wrote:
It makes good sense to me that we (continue to) track stripped files
at the same place as distributed files.
On the other hand, I don't see the point of using
Lars Wirzenius l...@liw.fi writes:
Dev-ref §6.7.8.2 recommends that if you have to repackage the original
source, that the transformations that are performed be recorded in
debian/copyright. While there was recently some discussion on d-devel
about whether repackaging just to remove
Lars Wirzenius l...@liw.fi writes:
If we do put the stripping information into debian/copyright, can
someone please suggest a concrete way to actually do that? What is
actually needed to implement the stripping automatically in
get-orig-source?
A free-form field into which I can put things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think at this point, we have to solve other problems with policy and
devref, and having solved them the correct outcome for DEP5 will become
obvious.
- if the transformation can be expressed as a script, use debian/rules
get-orig-source
Since
22 matches
Mail list logo
