From: | Ciaran McCreesh <ciaranm@×××××××.org> |
---|---|
To: | gentoo-dev@l.g.o |
Cc: | paludis-sekrit@×××××××××××××.de |
Subject: | [gentoo-dev] RFC: Package Manager Specification: configuration protection |
Date: | Mon, 11 Sep 2006 22:24:42 |
Message-Id: | 20060911232211.2cb55425@snowdrop.home |
1 | A while back it was agreed that it would be a good idea to standardise |
2 | certain aspects of package manager behaviour. We thought it'd be a good |
3 | idea to start with something easy so that we can iron out any kinks in |
4 | the process... So... |
5 | |
6 | Attached is a first draft of an attempt at standardising how |
7 | configuration protection is handled. Although it's not strictly |
8 | speaking a core part of the ebuild API, it's none the less something |
9 | that should probably be handled consistently. |
10 | |
11 | Comments both on the nature and the specifics of the specification |
12 | would be welcomed. In particular, I'd like to know if people think |
13 | we're mandating the appropriate degree of specificity and whether we're |
14 | providing sufficient generality to avoid overly restricting innovation. |
15 | |
16 | Yours lovingly, |
17 | -- |
18 | Ciaran McCreesh |
19 | Mail : ciaranm at ciaranm.org |
File name | MIME type |
---|---|
PMS-Configuration-Protection.txt | text/plain |
signature.asc | application/pgp-signature |
Subject | Author |
---|---|
Re: [gentoo-dev] RFC: Package Manager Specification: configuration protection | Chris White <chriswhite@g.o> |
Re: [gentoo-dev] RFC: Package Manager Specification: configuration protection | Michael Cummings <mcummings@g.o> |
Re: [gentoo-dev] RFC: Package Manager Specification: configuration protection | Simon Stelling <blubb@g.o> |
Re: [gentoo-dev] RFC: Package Manager Specification: configuration protection | Benno Schulenberg <benno.schulenberg@×××××.com> |
Re: [gentoo-dev] RFC: Package Manager Specification: configuration protection | "Harald van Dijk" <truedfx@g.o> |
Re: [gentoo-dev] RFC: Package Manager Specification: configuration protection | Brian Harring <ferringb@×××××.com> |