| 1 |
On Sun, 2022-12-25 at 18:02 +0000, m1027 wrote: |
| 2 |
> mgorny: |
| 3 |
> |
| 4 |
> > # Michał Górny <mgorny@g.o> (2022-12-25) |
| 5 |
> > # make.conf writing is broken and package.use support incomplete. |
| 6 |
> > # Last release in 2013. Attempted unsuccessfully fixing it in 2017. |
| 7 |
> > # Use an editor instead. |
| 8 |
> > # Removal on 2023-01-24. Bug #888423. |
| 9 |
> > app-portage/flaggie |
| 10 |
> |
| 11 |
> So I will deeply miss flaggie! Despite some issues it is a very |
| 12 |
> helpful thing once you know it, e.g. for automated USE flag changes |
| 13 |
> over ssh in a server farm. |
| 14 |
|
| 15 |
Hmm, that's a use case I didn't think of (and I didn't know anyone is |
| 16 |
actually using flaggie non-interactively). I guess most of the time you |
| 17 |
could get away with something like: |
| 18 |
|
| 19 |
echo app-foo/bar baz >> /etc/portage/package.use/local.conf |
| 20 |
|
| 21 |
etc. |
| 22 |
|
| 23 |
> I am rather in C than in python so I cannot really help advancing |
| 24 |
> flaggie. But I wonder whether there is a full specification for USE |
| 25 |
> in make.conf as well as for package.use/* so there was a chance to |
| 26 |
> think about a reimplementation somehow. |
| 27 |
|
| 28 |
To be honest, I'm thinking of starting from scratch like all cool |
| 29 |
programmers do these days. Perhaps I should aim for a very simple tool |
| 30 |
that doesn't try to represent all Portage configuration in AST |
| 31 |
and instead just does plain manipulations. So perhaps they'll |
| 32 |
be a flaggie2 after all. |
| 33 |
|
| 34 |
-- |
| 35 |
Best regards, |
| 36 |
Michał Górny |
Archives