[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Direct commits to packages' VCS (Was: DEP1: Non Maintainer Uploads)

On Tue, Aug 12, 2008 at 04:29:04PM -0300, Lucas Nussbaum wrote:
> >   `debian/README.source' may also include any other information that
> >   would be helpful to someone modifying the source package.
> Sure, but with the way the policy is currently written, it's still not
> the _main purpose_ of debian/README.source.

Ack. I indeed think the wording should be improvement, and IIRC Russ
acknowledge that. But right now it is how you said.

> Looking at the 306 source packages using README.source (see
> gluck:~lucas/readme.source), it's obvious that the lack of guidelines on
> how to use this file is limiting its usefulness (unless the goal is to
> generate lots of variants of quilt howtos ;)


> I don't garantee that I'll accept it, but could you prepare a patch
> that would mention README.source, staying vague on the gory details?
> You can use gluck:~lucas/pkgs.dbk as a basis.

Actually I had already thought about preparing the patch upon my first
post, but I refrained to do so because I didn't find the good place
where to mention it in the current DEP text. At a second look though,
the section "When and how to do an NMU" seems appropriate.

Patch attached.
(Note that I haven't tried building the resulting dbk.)


Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
I'm still an SGML person,this newfangled /\ All one has to do is hit the
XML stuff is so ... simplistic  -- Manoj \/ right keys at the right time
--- pkgs.dbk.orig	2008-08-13 16:44:44.000000000 -0600
+++ pkgs.dbk	2008-08-13 16:52:12.000000000 -0600
@@ -1892,6 +1892,14 @@
 might be helpful).
+While preparing the patch, you should better be aware of any package-specific
+practices that the maintainer might be using. Taking them into account reduces
+the burden of getting your changes integrated back in the normal package
+workflow and thus increases the possibilities that that will happen. A good
+place where to look for for possible package-specific practices is
+<ulink url="&url-debian-policy;ch-source.html#s-readmesource"><literal>debian/README.source</literal></ulink>.
 Unless you have an excellent reason not to do so, you must then give some time
 to the maintainer to react (for example, by uploading to the
 <literal>DELAYED</literal> queue).  Here are some delays that you could use as

Attachment: signature.asc
Description: Digital signature

Reply to: