1 |
Mike Frysinger wrote: |
2 |
|
3 |
> On Wednesday 25 April 2012 02:26:19 Steven J Long wrote: |
4 |
>> Mike Frysinger wrote: |
5 |
>> > Paul Varner wrote: |
6 |
>> >> Robin H. Johnson wrote: |
7 |
>> >> > Why are we keeping it? I move that we remove it. It's been replaced |
8 |
>> >> > by USE flags in metadata.xml for several years now. |
9 |
>> >> |
10 |
>> >> euse from gentoolkit still uses it since it is written in bash and XML |
11 |
>> >> parsing in bash can be problematic. We really need to get euse |
12 |
>> >> rewritten in python so it can use the portage and gentoolkit API's |
13 |
>> >> before we get rid of the file. |
14 |
>> > |
15 |
>> > it's also a bit of a speed issue. i often want to look at what flags |
16 |
>> > get used |
17 |
>> > across the tree. what's faster: loading + parsing 15000 xml files, or |
18 |
>> > loading 1 file ? shifting it to metadata/ as a cache of all the xml |
19 |
>> > files is probably fine, but i'm not sure dropping it completely is an |
20 |
>> > improvement. |
21 |
>> |
22 |
>> Agreed. I don't think it's a good idea to lose the ability to script |
23 |
>> against the tree from bash. |
24 |
> |
25 |
> technically, you can script with xml files just fine from bash. install |
26 |
> app- text/xmlstarlet and use the `xml` tool. |
27 |
|
28 |
Oh, I've been a fan for several years[1] :) I still don't want to require it |
29 |
as a dependency, especially when, as you say, it's quick and easy to access |
30 |
a single file per-repo. |
31 |
|
32 |
There's utility in it, and there isn't any real gain in ditching it, beyond |
33 |
not requiring its generation. And since it's been unnoticed for such a long |
34 |
while, it can't be causing any real troubles. So why lose its usefulness? |
35 |
|
36 |
It certainly counts as a file that should be synchronised as part of the |
37 |
repo, though. So if you're going to move it to /var, better to move |
38 |
/usr/portage itself, imo. |
39 |
|
40 |
(This thread feels like it's really about that, tbh, but users can already |
41 |
set it where they want and often just have a separate partition, or if |
42 |
they're bothered have already configured it to /var/portage, so it's more |
43 |
about new users, and whether a baselayout change is worth the hassle.) |
44 |
|
45 |
Regards, |
46 |
Steve. |
47 |
|
48 |
[1] cf: /msg friendlyToaster xml |
49 |
-- |
50 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |