On Sat, Dec 18, 2004 at 06:15:10PM -0800, Brian Nelson wrote:
...
First of all, I'll assume you've skimmed over the source as part of your
initial packaging. I usually go through the following steps:
...
Did I miss anything?
Pretty good. I added this and other post to maint-guide. OK to be
Hi,
On Sun, Dec 19, 2004 at 02:48:02AM +0200, Antti-Juhani Kaijanaho wrote:
Like with many other things in Debian, how you do it doesn't matter as
long as you don't break things. Things that should be considered
include:
- Use a -1 Debian revision number for the new upstream release.
-
On Wed, Dec 22, 2004 at 07:31:22PM -0800, Matt Zimmerman wrote:
On Mon, Dec 20, 2004 at 09:45:32PM -0500, Erinn Clark wrote:
* Brian Nelson [EMAIL PROTECTED] [2004:12:18 18:15 -0800]:
snip lots of stuff
Did I miss anything?
Yeah, the part where you turn this into a poster to be
On Sat, Dec 18, 2004 at 06:23:28PM -0500, Erinn Clark wrote:
After checking appropriate docs and asking around and getting different
answers, I thought I'd see if there was any consensus on this:
How do you deal with new upstream releases? The general answers I'm getting
seem to be along
On Mon, Dec 20, 2004 at 09:45:32PM -0500, Erinn Clark wrote:
* Brian Nelson [EMAIL PROTECTED] [2004:12:18 18:15 -0800]:
snip lots of stuff
Did I miss anything?
Yeah, the part where you turn this into a poster to be hung on my wall.
...and the unified diff for developers-reference. :-)
* Brian Nelson [EMAIL PROTECTED] [2004:12:18 18:15 -0800]:
snip lots of stuff
Did I miss anything?
Yeah, the part where you turn this into a poster to be hung on my wall.
Thank you! This is exactly what I wanted.
--
off the chain like a rebellious guanine nucleotide
signature.asc
Hi everyone,
After checking appropriate docs and asking around and getting different
answers, I thought I'd see if there was any consensus on this:
How do you deal with new upstream releases? The general answers I'm getting
seem to be along the lines of move the debian/ directory to the new
* Erinn Clark [EMAIL PROTECTED] [2004:12:18 18:23 -0500]:
snip
Of course, just after sending this mail, I was directed to:
http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream
...which I somehow managed to miss. It's still a bit sparse, so any other
tips people have for
On 20041218T182328-0500, Erinn Clark wrote:
How do you deal with new upstream releases? The general answers I'm getting
seem to be along the lines of move the debian/ directory to the new
release and tweak it til things work. Is this correct? If so (or if not),
shouldn't there be something in
On Sun, Dec 19, 2004 at 02:48:02AM +0200, Antti-Juhani Kaijanaho wrote:
Like with many other things in Debian, how you do it doesn't matter as
long as you don't break things. Things that should be considered
include:
- Use a -1 Debian revision number for the new upstream release.
-
On Sat, 18 Dec 2004, Erinn Clark wrote:
How do you deal with new upstream releases? The general answers I'm getting
I'd suggest using a version control system (even a lame one such as CVS), so
that you know exactly what changed from one upstream to another, and update
the debian/ stuff and any
* Henrique de Moraes Holschuh [EMAIL PROTECTED] [2004:12:18 23:53 -0200]:
On Sat, 18 Dec 2004, Erinn Clark wrote:
How do you deal with new upstream releases? The general answers I'm getting
I'd suggest using a version control system (even a lame one such as CVS), so
that you know exactly
Erinn Clark [EMAIL PROTECTED] writes:
* Erinn Clark [EMAIL PROTECTED] [2004:12:18 18:23 -0500]:
snip
Of course, just after sending this mail, I was directed to:
http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream
...which I somehow managed to miss. It's still a bit
13 matches
Mail list logo
