From: maximilian attems <max@stro.at>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kbuild@vger.kernel.org,
Andres Salomon <dilinger@debian.org>,
tytso@mit.edu, sam@ravnborg.org
Subject: Re: Comments on deb-pkg patch series
Date: Wed, 1 Apr 2009 20:47:55 +0200 [thread overview]
Message-ID: <20090401184755.GC3901@baikonur.stro.at> (raw)
In-Reply-To: <200904012035.58852.elendil@planet.nl>
On Wed, Apr 01, 2009 at 08:35:57PM +0200, Frans Pop wrote:
> On Wednesday 01 April 2009, maximilian attems wrote:
> > > Technically it does not matter, correct. But for the same reason
> > > there is also no good reason to make it the same as the debian linux
> > > images source package.
> > >
> > > And as it is factually incorrect I still don't like it. It would very
> > > simply result in incorrect info if people query their system using
> > > tools like grep-dpkg, or even if they just just view the package
> > > info.
> [...]
> > so i still miss your point why make deb-pkg shouldn't show that too!
>
> See quoted text above. Even if a binary package _can_ be built from the
> linux-2.6 source package using deb-pkg, in almost all cases that will
> _not_ be the case. For me that in itself is sufficient reason not to
> set "Source: linux-2.6". It very simply does not reflect the truth.
please get your linux-2.6 debianism out of your head. yes most of
the time make deb-pkg will be used by an upstream tarball or git tree.
it will certainly *not* be build by the "source" package linux.
so that is certainly wrong.
i repeat my argument that you have to go for the general case of
linux-2.6, so it will be correct in many cases instead of beeing
always incorrect.
> > btw this patch also fixes wrong section behaviour of make deb-pkg.
>
> Ah, yes. I forgot about that. I do agree with that part of the patch.
>
> With the recent restructuring of the archive the correct section for
> kernel packages would be "kernel" and not "admin", but for deb-pkg we
> probably should postpone that change for a few years as "kernel" is not
> yet valid for stable and oldstable.
ack, right.
next prev parent reply other threads:[~2009-04-01 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 16:07 Comments on deb-pkg patch series Frans Pop
2009-04-01 16:23 ` maximilian attems
2009-04-01 17:07 ` Frans Pop
2009-04-01 17:32 ` maximilian attems
2009-04-01 17:53 ` Frans Pop
2009-04-01 17:57 ` maximilian attems
2009-04-01 18:35 ` Frans Pop
2009-04-01 18:47 ` maximilian attems [this message]
2009-04-01 19:11 ` Frans Pop
2009-04-01 19:21 ` maximilian attems
2009-04-05 19:38 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090401184755.GC3901@baikonur.stro.at \
--to=max@stro.at \
--cc=dilinger@debian.org \
--cc=elendil@planet.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox