From: Herve Eychenne <rv@wallfire.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: Call for testing: patch-o-matic-ng
Date: Mon, 5 Jan 2004 14:22:56 +0100 [thread overview]
Message-ID: <20040105132256.GA4074@eychenne.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0401051336400.15139-100000@blackhole.kfki.hu>
On Mon, Jan 05, 2004 at 01:45:46PM +0100, Jozsef Kadlecsik wrote:
> Hi Herve,
> On Mon, 5 Jan 2004, Herve Eychenne wrote:
> > I think the convention of Debian Packages files with a line like
> > Depends: zope, python2.1-popy (>= 2.0.8), python2.1-popy (<< 2.0.9)
> > would just be perfect.
> No, that's not so simple. I had just convinced Harald (:-) that we should
> keep the different versions of the same patch in one directory, like:
> foo/
> foo/info # Common auxiliary files
> foo/help
> foo/linux-2.4.patch # 2.4 speficic patch and whole files
> foo/linux-2.4/...
> foo/linux-2.6.patch # 2.6 specific patch and whole files
> foo/linux-2.6/...
> The Requires (in your context: Depends) lines can be added to the info
> file, which thus valid for all patch-versions. In Debian, you have one
> specific package. Here we have multiple versions of the same patch.
It's pretty much the same as the Debian scheme.
A Debian package name is equivalent to your "foo". Several
versions of it may exist at the same time.
Debian has several files (.deb) containing a package name and version.
A "Packages" file is computed based on that files.
Your "info" is the equivalent of a single entry in the Debian Packages
file, no problem...
Your "linux-2.4" is the equivalent of the package-version.deb
Your "help" could probably be integrated into "info".
So I see no problem with your scheme. Yet, what would you put in
"linux-2.4/..."? Why doesn't it get into linux-2.4.patch?
I would have thought about a single file for each foo-version, which
would be called foo-version.pom
Each file would contain:
<<<<<<<<<<<<<<<< CUT HERE >>>>>>>>>>>>>>>>>>
Module: foo
Section: extra
Author: ...
...
Version: 2.4.3 # note: version of the module, not of the kernel)
Depends: nat (>= 0.9.0), linux (>= 2.4.22)
Description: the foo module adds ...
<the diff itself>
<<<<<<<<<<<<<<<< CUT HERE >>>>>>>>>>>>>>>>>>
And you could have at the same time, if needed:
<<<<<<<<<<<<<<<< CUT HERE >>>>>>>>>>>>>>>>>>
Module: foo
Section: extra
Author: ...
...
Version: 2.6.3
Depends: nat (>= 1.0.0), linux (>= 2.6.0)
Description: the foo module adds ...
<the diff itself>
<<<<<<<<<<<<<<<< CUT HERE >>>>>>>>>>>>>>>>>>
Everything in a flat directory... Or you can create a section
directory, like the old system.
Or even create a directory per module, if you want, so you can factorize
Module name and Description fields.
Well... do as you please.
Herve
--
_
(°= Hervé Eychenne
//)
v_/_ WallFire project: http://www.wallfire.org/
next prev parent reply other threads:[~2004-01-05 13:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031229154612.GB1417@obroa-skai.de.gnumonks.org>
[not found] ` <Pine.LNX.4.33.0312310923090.9991-100000@blackhole.kfki.hu>
2004-01-01 16:36 ` Call for testing: patch-o-matic-ng Harald Welte
2004-01-05 11:32 ` Jozsef Kadlecsik
2004-01-05 11:55 ` Herve Eychenne
2004-01-05 12:03 ` Harald Welte
2004-01-05 12:45 ` Jozsef Kadlecsik
2004-01-05 13:22 ` Herve Eychenne [this message]
2004-01-06 10:32 ` Jozsef Kadlecsik
2004-01-06 13:37 ` Herve Eychenne
2004-01-05 15:28 ` Henrik Nordstrom
2003-12-24 2:30 Vilmos Branyik
-- strict thread matches above, loose matches on Subject: below --
2003-12-21 12:24 Harald Welte
2003-12-22 9:56 ` KOVACS Krisztian
2003-12-22 12:00 ` Harald Welte
2003-12-23 13:13 ` Gaël Le Mignot
2003-12-23 17:30 ` Harald Welte
2003-12-23 18:56 ` Unknown, Alistair Tonner
2003-12-24 0:26 ` Gaël Le Mignot
2003-12-24 1:03 ` Unknown, Alistair Tonner
2003-12-24 1:03 ` Unknown, Alistair Tonner
[not found] ` <200312231356.17135.Alistair Tonner <>
[not found] ` <200312231356.17135.AlistairTonner<>
2003-12-25 9:06 ` Galtar
2003-12-25 9:41 ` Antony Stone
2004-01-02 12:41 ` Henrik Nordstrom
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=20040105132256.GA4074@eychenne.org \
--to=rv@wallfire.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.