Re: RFS: b5

2006-03-21 Thread Panu Kalliokoski
On Tue, Mar 14, 2006 at 12:05:21AM +0100, Michelle Konzack wrote: > I have a script which do: [...] > 1) Create a directory with the source and a debian/ directors > 2) cd into the source root to create a "pristine" package > 3) type: tdbuildpackage --make-orig FYI, I'm doing this now with ma

Re: RFS: b5

2006-03-17 Thread Michelle Konzack
Hi Panu, Am 2006-02-28 19:18:31, schrieb Panu Kalliokoski: > Thank you for this explanation. Although I still have some issues with > it, it seems I should build infrastructure for building source packages. > (Earlier, one just needed dpkg-source -b; now it seems there must be > some script or m

Re: RFS: b5

2006-03-17 Thread Michelle Konzack
Hello Panu, A little bit late, but was over 2 weeks not @home... Am 2006-02-28 19:31:22, schrieb Panu Kalliokoski: > I'm familiar with this section, but it does not say so, and it isn't > true that native packages can't be pristine: my .tar.gz's are pristine, > and they build native packages. H

Re: RFS: b5

2006-03-01 Thread Panu Kalliokoski
On Wed, Mar 01, 2006 at 04:57:15PM +, Jon Dowland wrote: > > But when the package is native, you get to real _all_ changes in > > changelog, so the situation is at least not worse in that case? > It depends on if you wanted to read the `upstream' changes or not :) > What are you currently putti

Re: RFS: b5

2006-03-01 Thread Jon Dowland
On Tue, Feb 28, 2006 at 07:41:43PM +0200, Panu Kalliokoski wrote: > But when the package is native, you get to real _all_ changes in > changelog, so the situation is at least not worse in that case? It depends on if you wanted to read the `upstream' changes or not :) What are you currently putting

Re: RFS: b5, bfc, python-selecting, stx2any, sokoedit

2006-03-01 Thread Panu Kalliokoski
I have updated these packages to build separate .orig.tar.gz and .diff.gz sources. Panu -- personal contact: [EMAIL PROTECTED], +35841 5323835 technical contact: [EMAIL PROTECTED], http://www.iki.fi/atehwa/ PGP fingerprint:0EA5 9D33 6590 FFD4 921C 5A5F BE85 08F1 3169 70EC -

Re: RFS: b5

2006-03-01 Thread Thijs Kinkhorst
On Wed, 2006-03-01 at 09:13 +0200, Panu Kalliokoski wrote: > It seems the only sensible way, then, because I really want to include > the debian/ files in my real release (they contain possibly useful > metadata, like the changelog, after all). You would best place the changelog in the root of you

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Tue, Feb 28, 2006 at 07:32:28PM +0100, Bas Wijnen wrote: > Oh no, please don't. You should use the same release tarball for Debian that > you actually release. That's what "pristine source tarball" means. If you That's what I thought, too. I just happened to think that it also implies that

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Tue, Feb 28, 2006 at 07:55:35PM -0500, Justin Pryzby wrote: > > Thank you for this explanation. Although I still have some issues with > > it, it seems I should build infrastructure for building source packages. > > (Earlier, one just needed dpkg-source -b; now it seems there must be > > some s

Re: RFS: b5

2006-02-28 Thread Jeroen van Wolffelaar
On Tue, Feb 28, 2006 at 07:55:35PM -0500, Justin Pryzby wrote: > On Tue, Feb 28, 2006 at 07:18:31PM +0200, Panu Kalliokoski wrote: > > On Wed, Mar 01, 2006 at 03:52:04AM +1100, skaller wrote: > > > > It's your call, but since making them non-native is not really that much > > > > more work, I'd rec

Re: RFS: b5

2006-02-28 Thread Justin Pryzby
On Tue, Feb 28, 2006 at 07:18:31PM +0200, Panu Kalliokoski wrote: > On Wed, Mar 01, 2006 at 03:52:04AM +1100, skaller wrote: > > > It's your call, but since making them non-native is not really that much > > > more work, I'd recommend doing it that way. > > However there is a reason, it is politica

Re: RFS: b5

2006-02-28 Thread skaller
On Tue, 2006-02-28 at 19:18 +0200, Panu Kalliokoski wrote: > On Wed, Mar 01, 2006 at 03:52:04AM +1100, skaller wrote: > > > It's your call, but since making them non-native is not really that much > > > more work, I'd recommend doing it that way. > > However there is a reason, it is political, it i

Re: RFS: b5

2006-02-28 Thread Bas Wijnen
On Tue, Feb 28, 2006 at 08:12:45PM +0200, Panu Kalliokoski wrote: > On Tue, Feb 28, 2006 at 06:57:38PM +0100, Bas Wijnen wrote: > > Having the debian/ directory under version control is useful. But it > > shouldn't be included in the tarball when you run "make dist". > > I've never used "make dis

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Tue, Feb 28, 2006 at 06:57:38PM +0100, Bas Wijnen wrote: > I see what you mean. However, both from a technical point of view, and from a > philosophical point of view, it makes sense: People who are getting your > release tarball will not want to build a Debian package (if they did, they'd > ge

Re: RFS: b5

2006-02-28 Thread skaller
On Tue, 2006-02-28 at 17:12 +0100, Thijs Kinkhorst wrote: > It's your call, but since making them non-native is not really that much > more work, I'd recommend doing it that way. It can be quite a lot more work if you have powerful scripts that can generate the required meta-information during t

Re: RFS: b5

2006-02-28 Thread Bas Wijnen
Hi, On Tue, Feb 28, 2006 at 07:18:31PM +0200, Panu Kalliokoski wrote: > On Wed, Mar 01, 2006 at 03:52:04AM +1100, skaller wrote: > Thank you for this explanation. Although I still have some issues with > it, it seems I should build infrastructure for building source packages. > (Earlier, one just

Re: RFS: b5

2006-02-28 Thread Thijs Kinkhorst
On Wed, 2006-03-01 at 03:52 +1100, skaller wrote: > On Tue, 2006-02-28 at 17:12 +0100, Thijs Kinkhorst wrote: > > > It's your call, but since making them non-native is not really that much > > more work, I'd recommend doing it that way. > > It can be quite a lot more work if you have powerful scr

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Tue, Feb 28, 2006 at 04:27:00PM +, Jon Dowland wrote: > > Really? I've never seen such a guideline (although I admit it's been > > a long time since I read the relevant documents). In fact, the Debian > > Developer's Reference, section 5.4, seems to suggest that the > > difference is purel

Re: RFS: b5

2006-02-28 Thread Jon Dowland
On Tue, Feb 28, 2006 at 05:55:13PM +0200, Panu Kalliokoski wrote: > Really? I've never seen such a guideline (although I admit it's been > a long time since I read the relevant documents). In fact, the Debian > Developer's Reference, section 5.4, seems to suggest that the > difference is purely t

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Tue, Feb 28, 2006 at 11:05:32AM -0500, Justin Pryzby wrote: > I think the reason is that native packages can't be pristine, and > pristine packages are preferred. > > http://www.us.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-origtargz I'm familiar with this sec

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Wed, Mar 01, 2006 at 03:52:04AM +1100, skaller wrote: > > It's your call, but since making them non-native is not really that much > > more work, I'd recommend doing it that way. > However there is a reason, it is political, it is > relevant -- it convinced me anyhow :) I also initially > produc

Re: RFS: b5

2006-02-28 Thread Justin Pryzby
On Tue, Feb 28, 2006 at 05:55:13PM +0200, Panu Kalliokoski wrote: > On Tue, Feb 28, 2006 at 04:32:16PM +0100, Thijs Kinkhorst wrote: > > Native packages should ideally only be packages that have no real use > > outside of Debian. > > Really? I've never seen such a guideline (although I admit it's

Re: RFS: b5

2006-02-28 Thread Justin Pryzby
On Tue, Feb 28, 2006 at 04:32:16PM +0100, Thijs Kinkhorst wrote: > Hello Panu, > > On Tue, 2006-02-28 at 16:05 +0200, Panu Kalliokoski wrote: > > Where to get it: > > http://sange.fi/~atehwa/debian/b5_2.3.dsc > > http://sange.fi/~atehwa/debian/b5_2.3.tar.gz > > http://sange.fi/~atehwa/debian/b5_2.

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Wed, Mar 01, 2006 at 12:09:49AM +0800, Ying-Chun Liu wrote: > >>Native packages should ideally only be packages that have no real use > >>outside of Debian. [...] > > If you could show me some document that explains whether and why > > native packages are not preferred for software that could li

Re: RFS: b5

2006-02-28 Thread Thijs Kinkhorst
On Tue, 2006-02-28 at 17:55 +0200, Panu Kalliokoski wrote: > On Tue, Feb 28, 2006 at 04:32:16PM +0100, Thijs Kinkhorst wrote: > > Native packages should ideally only be packages that have no real use > > outside of Debian. > > Really? I've never seen such a guideline (although I admit it's been a

Re: RFS: b5

2006-02-28 Thread Ying-Chun Liu
Panu Kalliokoski wrote: > On Tue, Feb 28, 2006 at 04:32:16PM +0100, Thijs Kinkhorst wrote: > >>Native packages should ideally only be packages that have no real use >>outside of Debian. > > > Really? I've never seen such a guideline (although I admit it's been a > long time since I read the rel

Re: RFS: b5

2006-02-28 Thread Panu Kalliokoski
On Tue, Feb 28, 2006 at 04:32:16PM +0100, Thijs Kinkhorst wrote: > Native packages should ideally only be packages that have no real use > outside of Debian. Really? I've never seen such a guideline (although I admit it's been a long time since I read the relevant documents). In fact, the Debian

Re: RFS: b5

2006-02-28 Thread Thijs Kinkhorst
Hello Panu, On Tue, 2006-02-28 at 16:05 +0200, Panu Kalliokoski wrote: > Where to get it: > http://sange.fi/~atehwa/debian/b5_2.3.dsc > http://sange.fi/~atehwa/debian/b5_2.3.tar.gz > http://sange.fi/~atehwa/debian/b5_2.3_all.deb > http://sange.fi/~atehwa/debian/b5_2.3_i386.changes The same goes f