From: Frans Pop <elendil@planet.nl>
To: maximilian attems <max@stro.at>
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 21:11:09 +0200 [thread overview]
Message-ID: <200904012111.11664.elendil@planet.nl> (raw)
In-Reply-To: <20090401184755.GC3901@baikonur.stro.at>
This is going to be my last post about this as we're in danger of
repeating ourselves. IMO the arguments are now clear; others will have
to make the decision here.
On Wednesday 01 April 2009, maximilian attems wrote:
> 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.
Right. But IMO listing a non-existent source package is actually *better*
because a .deb built using deb-pkg per definition does not _have_ a
source package.
> 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.
linux-2.6 is not the general case, it is an exception. The general case is
building from some upstream git branch. (Unless you mean the linux-2.6
git tree, but that is totally irrelevant as it's not a source _package_.)
The fact that the package refers to a non-existant source package has an
informational value in itself and because there *is* no source package,
it is perfectly correct.
It would be better to not list a source package at all, but that's
impossible due to technical requirements.
As mentioned before, IMO "Source: linux-upstream" would be a better
choice.
next prev parent reply other threads:[~2009-04-01 19:11 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
2009-04-01 19:11 ` Frans Pop [this message]
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=200904012111.11664.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=dilinger@debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
--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