Russ Allbery wrote:
> Also, for a Git repository, what do you do if the Debian packaging isn't
> on the master branch? For example, for packages for which I'm also
> upstream, I do upstream development on the master branch and Debian
> packaging on a separate debian branch.
I wonder if something
Jonathan Nieder writes:
> If I keep my sources in svn, should I give a URL to the toplevel of the
> repository (which is what one passes to "git svn clone -s" and allows
> access to all branches) or one particular branch?
For debcheckout to work properly, you want to specify a branch.
> If a br
Hi Charles,
Charles Plessy wrote:
> +
> + Vcs-arch, Vcs-bzr (Bazaar), Vcs-cvs,
> + Vcs-darcs, Vcs-git, Vcs-hg
> + (Mercurial), Vcs-mtn (Monotone), Vcs-svn
> + (Subversion)
> +
> +
> +
> + S
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was r...@debian.org).
> limit package debian-policy
Limiting to bugs with field 'package' containing at least one of 'debian-policy'
Limit currently set to '
Package: debian-policy
Version: 3.9.2.0
Severity: normal
Dear all,
now that thousands of pakcages use the VCS fields, I think that it is time to
document them in the Policy. Please see the attached patch as a starting
point.
The Developers Reference already documents the VCS fields, and discuss
Charles Plessy writes:
> There have been recurrent discussions about
> /usr/share/doc/package-doc being a symbolic link to
> /usr/share/doc/package. In my understanding, this is
> discouraged now. Perhaps this desserves a footnote ?
I tried to avoid changing anything in this area because we ha
Le Fri, Jan 06, 2012 at 09:13:13AM -0800, Russ Allbery a écrit :
>
> Discussion, objections, seconds?
Dear Russ,
overall, I am very positive with your changes, but here are two comments that I
hope can improve the section.
> +
> + Any separate package providing documentation must sti
Jonathan Nieder writes:
> Russ Allbery wrote:
> [...]
>>
>> - It is often a good idea to put text information files
>> - (READMEs, changelogs, and so forth) that come with
>> - the source package in /usr/share/doc/package
>> - in the binary package.
>> +
Hi,
Russ Allbery wrote:
> * Some reorganization and wording tweaks to hopefully make things clearer.
Alas, there's a lot of this --- enough that I wish this had been
prepared as a multiple-patch series, with for example whitespace-only
changes split out.
Oh, well. Onward. :)
[...]
> --- a/pol
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was r...@debian.org).
> limit package debian-policy
Limiting to bugs with field 'package' containing at least one of 'debian-policy'
Limit currently set to '
As always, once I start seriously poking at an area of Policy, I see other
little things that need to be fixed as well. Here is a general overhaul
of the additional documentation section, which should both address this
bug as well as a few other things.
The changes here are:
* Shared library doc
Niko Tyni writes:
> I'm OK with the wording about 'Configuration Modules', and I agree that
> Debian packages should not ship regular modules in /etc/perl. Maybe a
> footnote about recommending other configuration formats over arbitrary
> Perl code would alleviate Steve's concern?
Yeah, we coul
On Fri, 2012-06-01 at 10:07 +0200, Niko Tyni wrote:
> As for libnet.cfg and ParserDetails.ini, both of those seem to me more
> like minor bugs than something to bless in Policy. They could equally
> well (barring transition issues) go in something like /etc/libnet-perl
> and /etc/libxml-sax-perl AF
On Thu, Jan 05, 2012 at 06:15:41PM +, Dominic Hargreaves wrote:
> On Thu, Jan 05, 2012 at 09:07:38AM -0800, Russ Allbery wrote:
> > Dominic Hargreaves writes:
> >
> > > There are a couple of other things which use /etc/perl, from only a
> > > brief look at the perl debian/changelog (/etc/perl
14 matches
Mail list logo
