Re: Documentation on package maintenance
- To: Joachim Zobel <jz-2013@heute-morgen.de>
- Cc: Debian Java List <debian-java@lists.debian.org>
- Subject: Re: Documentation on package maintenance
- From: tony mancill <tony@mancill.com>
- Date: Sun, 29 Sep 2013 09:20:07 -0700
- Message-id: <[🔎] 52485337.2090406@mancill.com>
- In-reply-to: <[🔎] 1380300326.4353.5.camel@backspace.crrrwg.de>
- References: <[🔎] 1380300326.4353.5.camel@backspace.crrrwg.de>
On 09/27/2013 09:45 AM, Joachim Zobel wrote: > Hi. > > Is there any documentation on maintaining existing packages. The docs I > find focus on how to create a package. I myself currently try to find > out how the netbeans package from git works. I will find out, but it > could be a lot easier with a few one liners and a short explanation of > their context. > > Sincerely, > Joachim Hi Joachim, Although it may not seem like it, most of the simpler team-maintained packages follow a consistent process for building. (We could do a better job of documenting that process on the wiki, though.) Larger, more complex packages can be a different story. Oftentimes the build process is documented in README.source, as recommended by policy [1]. However, in practice, these files are often out of date. In the case of packages that don't build in the standard way (everything should build with "debuild -us -uc"), I'd suggest contacting the maintainers and/or filing a severity wishlist bug report against the source package requesting the addition of the file. Cheers, tony [1] http://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource
Reply to:
- References:
- Documentation on package maintenance
- From: Joachim Zobel <jz-2013@heute-morgen.de>
- Documentation on package maintenance
- Prev by Date: RFS: antlr3 3.2-9
- Next by Date: Re: RFS: antlr3 3.2-9 - [UPLOADED]
- Previous by thread: Documentation on package maintenance
- Next by thread: RFS: jpathwatch 0.95-1 (new)
- Index(es):