1 |
On Thu, 18 Mar 2004 20:46:29 +0100 |
2 |
Olivier Crête <tester@g.o> wrote: |
3 |
|
4 |
> I just re-read glep 5 and I noticed a problem with it. It proposes |
5 |
> moving the licensing information to metadata.xml. |
6 |
|
7 |
I've just read glep 5, and i'm a bit sceptical about it. I'm not a |
8 |
dev so i currently don't have to touch metadata.xml, but only ebuilds |
9 |
(quick bump in my overlays, sometimes writing new ones, etc.), and i |
10 |
like it this way. But if this glep gets accepted, i will have to write |
11 |
a metadata.xml for every new package i do, and i don't really understand |
12 |
why. I think that, despite it "simplify the ebuild format", it would |
13 |
complicates the overall process of writing new packages (two different |
14 |
syntax, two skeletons, etc.), of sharing them beetween users, of |
15 |
submitting them to bugzilla (expect many submissions with missing |
16 |
metadatas), etc. That's all very minor issues, but still annoyances. |
17 |
Declaring the bash way three variables in an already opened file is |
18 |
already the simplest thing i can think of, and writing them in a |
19 |
separate xml file is not. |
20 |
|
21 |
I have the fealing that the motivation is a bit theoretical: avoiding |
22 |
redundancy because it is a well known ugly/bad thing. If it is the |
23 |
case, i don't really agree, this should not be a goal by itself. |
24 |
Redundancy is bad when it makes things harder to maintain, or when it |
25 |
implies tricky code to ensure coherence, etc. But here, there is no such |
26 |
issue: |
27 |
- on maintenance side, there is no difference ; when you have a |
28 |
new version to write you start with a copy of the previous one, so the |
29 |
description/homepage/license are not additional work. |
30 |
- and on the code side, as Marius explained, it would complicates |
31 |
things. |
32 |
|
33 |
So what did i miss something that would justify this changes? |
34 |
|
35 |
Thanks, |
36 |
|
37 |
-- |
38 |
TGL. |
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |