On Sat, Aug 25, 2012 at 05:18:57PM +0900, Charles Plessy wrote:
> I also considered, but the information of what files are excluded when
> creating
> the Debian source package is not relevant to upstream.
>
> More simply, I think that if debian/watch would radically change its format to
> YAML or
On Sat, Aug 25, 2012 at 12:34:28PM +0200, Jonas Smedegaard wrote:
> Hi Charles,
>
> On 12-08-25 at 01:03pm, Charles Plessy wrote:
> > a paragraph must not contain multiple instances of the same field.
>
> Interesting. Where is that defined?
Policy, 5.1, "Syntax of control files"
(http://www.deb
Hi Charles,
On 12-08-25 at 01:03pm, Charles Plessy wrote:
> a paragraph must not contain multiple instances of the same field.
Interesting. Where is that defined?
- Jonas
P.S.
I realize now that in this conversations I've wrongly used "section"
when referring to "paragraph", and "paragraph
On 12-08-24 at 01:06pm, Stefano Zacchiroli wrote:
> On Fri, Aug 24, 2012 at 12:33:09PM +0200, Jonas Smedegaard wrote:
> > > Files-Excluded:
> > > # ignore copy of lua
> > > lua_5.1.4/
> […]
> > Above means inventing a *new* syntax for files, instead of reusing
> > the existing one from Fil
Le Sat, Aug 25, 2012 at 07:24:06AM +0200, Andreas Tille a écrit :
> On Sat, Aug 25, 2012 at 01:03:03PM +0900, Charles Plessy wrote:
>
> > I also think that the current proposal would be a good opportunity to
> > transfer
> > the information about source location and excluded files in a separate f
On Sat, Aug 25, 2012 at 01:03:03PM +0900, Charles Plessy wrote:
> > So would be nice to check that the implementation properly includes all
> > of the following items:
> >
> > Format:
> > http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> > Source: http://susy.oddbird.net/
> >
> On 12-08-22 at 09:39am, Paul Wise wrote:
> >
> > In comparison to the current method for repacking (debian/rules
> > get-orig-source), this doesn't allow per-file-set comments about why
> > the file-set is being removed. I often use this to document in more
> > detail why I am removing files. So
On Fri, Aug 24, 2012 at 01:06:14PM +0200, Stefano Zacchiroli wrote:
> > Above means inventing a *new* syntax for files, instead of reusing the
> > existing one from Files: paragraphs.
>
> debian/control, which is 822-like, already supports #-comments. So,
> strictly speaking, we will just reusing
On Fri, Aug 24, 2012 at 12:33:09PM +0200, Jonas Smedegaard wrote:
> > Files-Excluded:
> > # ignore copy of lua
> > lua_5.1.4/
[…]
> Above means inventing a *new* syntax for files, instead of reusing the
> existing one from Files: paragraphs.
debian/control, which is 822-like, already supp
On 12-08-24 at 11:16am, Andreas Tille wrote:
> Hi Paul,
>
> On Wed, Aug 22, 2012 at 09:39:00AM +0800, Paul Wise wrote:
> > On Tue, Aug 21, 2012 at 6:21 PM, Andreas Tille wrote:
> >
> > > Any further hints / remarks?
> >
> > In comparison to the current method for repacking (debian/rules
> > get-
On 12-08-24 at 11:28am, Andreas Tille wrote:
> On Fri, Aug 24, 2012 at 10:59:10AM +0200, Jonas Smedegaard wrote:
> > > Anyway, I thought I wanted a separate file, but then I remembered that
> > > uscan already uses 'debian/watch' for configuration. The syntax of a
> > > watch file is pretty awkw
On Fri, Aug 24, 2012 at 10:59:10AM +0200, Jonas Smedegaard wrote:
> > Anyway, I thought I wanted a separate file, but then I remembered that
> > uscan already uses 'debian/watch' for configuration. The syntax of a
> > watch file is pretty awkward, being based on (logical) lines rather
> > than
On Thu, Aug 23, 2012 at 05:15:35PM -0500, Peter Samuelson wrote:
> Well, two reasons not to bundle it into DEP-5 format files. First,
> there may be a lot of people like me who would find value in a
> config-file-driven 'get-orig-source' but who do not find any value in
> maintaining debian/copyri
Hi Paul,
On Wed, Aug 22, 2012 at 09:39:00AM +0800, Paul Wise wrote:
> On Tue, Aug 21, 2012 at 6:21 PM, Andreas Tille wrote:
>
> > Any further hints / remarks?
>
> In comparison to the current method for repacking (debian/rules
> get-orig-source), this doesn't allow per-file-set comments about wh
On 12-08-23 at 05:15pm, Peter Samuelson wrote:
>
> > > Automating get-orig-source is a fine idea, but tying it to DEP-5
> > > would be unfortunate.
>
> [Jonas Smedegaard]
> > You mean that you prefer a separate file for this info?
> >
> > What should be its name? What should be its syntax?
> >
On Thu, Aug 23, 2012 at 12:38:14PM -0500, Peter Samuelson wrote:
> ...Or add the exclude list to a file called 'debian/watch'.
I struggle to see why. I suppose because uscan reads debian/watch, but
the point of that file is to document where to find upstream sources,
the name implies that, and put
> > Automating get-orig-source is a fine idea, but tying it to DEP-5
> > would be unfortunate.
[Jonas Smedegaard]
> You mean that you prefer a separate file for this info?
>
> What should be its name? What should be its syntax?
>
> ...and why start from scratch with this - or does something els
* Jonas Smedegaard , 2012-08-23, 19:47:
This is valid DEP-5 syntax as well:
Format:
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Source: http://susy.oddbird.net/
Repackaged, excluding non-DFSG licensed fonts and source-less
JavaScript
# Exlude source-less JavaScript
Files-
On 12-08-23 at 12:27pm, Peter Samuelson wrote:
>
> [Jonas Smedegaard]
> > Format:
> > http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> > Source: http://susy.oddbird.net/
> > Repackaged, excluding non-DFSG licensed fonts and source-less
> > JavaScript
> > Files-Excluded:
>
[Peter Samuelson]
> And there is something to be said for the dpkg-source / debhelper
> style, in which each configuration parameter lives in its own tiny
> file (e.g., 'debian/source/format', 'debian/compat',
> 'debian/pyversions') rather than as fields of a larger file that is
> only tangentiall
[Jonas Smedegaard]
> Format:
> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> Source: http://susy.oddbird.net/
> Repackaged, excluding non-DFSG licensed fonts and source-less
> JavaScript
> Files-Excluded:
> docs/source/javascripts/jquery-1.7.1.min.js
> docs/source/j
On 12-08-21 at 12:21pm, Andreas Tille wrote:
> Regarding the implementation there was some uncertainity about the
> actual Perl module to use. In the attached example script I decided
> to stick to Dpkg::Control and left the code for Parse::DebControl as a
> comment which could pretty easily co
On 12-08-22 at 09:39am, Paul Wise wrote:
> On Tue, Aug 21, 2012 at 6:21 PM, Andreas Tille wrote:
>
> > Any further hints / remarks?
>
> In comparison to the current method for repacking (debian/rules
> get-orig-source), this doesn't allow per-file-set comments about why
> the file-set is being re
On Tue, Aug 21, 2012 at 6:21 PM, Andreas Tille wrote:
> Any further hints / remarks?
In comparison to the current method for repacking (debian/rules
get-orig-source), this doesn't allow per-file-set comments about why
the file-set is being removed. I often use this to document in more
detail why
Charles Plessy writes:
> Le Tue, Aug 21, 2012 at 03:48:33PM +0200, Andrew Shadura a écrit :
>> By the way, how about adding something under debian/source/... to allow
>> automatic repacking regardless of Files-Excluded? (Or please tell me
>> how to repack upstream's zipball to targz automatically
Le Tue, Aug 21, 2012 at 03:48:33PM +0200, Andrew Shadura a écrit :
>
> By the way, how about adding something under debian/source/... to allow
> automatic repacking regardless of Files-Excluded? (Or please tell me
> how to repack upstream's zipball to targz automatically without having
> to specif
On Tue, Aug 21, 2012 at 03:40:41PM +0200, olivier sallou wrote:
>
> Just a remark, it would be nice in this case to get a warning/log that
> some/all glob do not match to track changes in upstream tarballs (exclusion
> in previous release, then not needed anymore).
Yes. Uscan does print several
On Tue, Aug 21, 2012 at 12:21:21PM +0200, Andreas Tille wrote:
> Any further hints / remarks?
... just a big THANKS for helping the discussion in this thread and for
the draft code! I totally agree with Jakub that the main issue here is
that repackaging is a PITA, fixing the tools is the way to go
On Tue, Aug 21, 2012 at 03:48:33PM +0200, Andrew Shadura wrote:
>
> By the way, how about adding something under debian/source/... to allow
> automatic repacking regardless of Files-Excluded? (Or please tell me
> how to repack upstream's zipball to targz automatically without having
> to specify -
Hello,
On Tue, 21 Aug 2012 12:21:21 +0200
Andreas Tille wrote:
> 2. If files matching are contained in the source tarball this will
> be repackaged except if the option --no-exclusion is given at
> uscan command line or if USCAN_NO_EXCLUSION is set in
> /etc/devscripts.conf or ~/.de
2012/8/21 Andreas Tille
> Hi,
>
> third summary of the proposal
>
> 1. The new field Files-Excluded in debian/copyright contains a space
> separated list of globs (as used by find and for specifying file
> lists in machine readable debian/control files). The deletion
> process will l
Andreas Tille writes:
> On Tue, Aug 21, 2012 at 01:25:26PM +0200, Simon Josefsson wrote:
>> How about resolving the empty directory problem by permitting the
>> Files-Excluded to match directories? Thus, if you want to remove the
>> docs/source/fonts/ hierarchy, you would instead write:
>>
>> F
Hi Charles,
On Tue, Aug 21, 2012 at 09:11:47PM +0900, Charles Plessy wrote:
> As suggested in http://lists.debian.org/2012081822.gt5...@jones.dk,
> something similar to the following two commands would do be compatible with
> the
> syntax of the Files field (although I am still unsure if a pr
Le Tue, Aug 21, 2012 at 12:21:21PM +0200, Andreas Tille a écrit :
>
> 1. The new field Files-Excluded in debian/copyright contains a space
> separated list of globs (as used by find and for specifying file
> lists in machine readable debian/control files). The deletion
> process will
On Tue, Aug 21, 2012 at 01:25:26PM +0200, Simon Josefsson wrote:
> How about resolving the empty directory problem by permitting the
> Files-Excluded to match directories? Thus, if you want to remove the
> docs/source/fonts/ hierarchy, you would instead write:
>
> Files-Excluded:
>docs/source
Andreas Tille writes:
> Files-Excluded:
> docs/source/fonts/*
> docs/source/javascripts/jquery-1.7.1.min.js
> docs/source/javascripts/modernizr-2.5.3.min.js
...
> Regarding the implementation there was some uncertainity about the
> actual Perl module to use. In the attached example script
On Tue, Aug 21, 2012 at 12:32:18PM +0200, Jakub Wilk wrote:
> * Andreas Tille , 2012-08-21, 12:21:
> >The new field Files-Excluded in debian/copyright contains a space
> >separated list of globs (as used by find and for specifying file
> >lists in machine readable debian/control files). The deletio
* Andreas Tille , 2012-08-21, 12:21:
The new field Files-Excluded in debian/copyright contains a space
separated list of globs (as used by find and for specifying file lists
in machine readable debian/control files). The deletion process will
loop over every expression
rm -rf ${MAIN_SOUR
Hi,
third summary of the proposal
1. The new field Files-Excluded in debian/copyright contains a space
separated list of globs (as used by find and for specifying file
lists in machine readable debian/control files). The deletion
process will loop over every expression
rm -rf
39 matches
Mail list logo
