# Michał Górny <mgorny@gentoo.org> (2022-12-25)
# make.conf writing is broken and package.use support incomplete.
# Last release in 2013.  Attempted unsuccessfully fixing it in 2017.
# Use an editor instead.
# Removal on 2023-01-24.  Bug #888423.
app-portage/flaggie

--
Best regards,
Michał Górny

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

mgorny:

# Michał Górny <mgorny@gentoo.org> (2022-12-25)
# make.conf writing is broken and package.use support incomplete.
# Last release in 2013.  Attempted unsuccessfully fixing it in 2017.
# Use an editor instead.
# Removal on 2023-01-24.  Bug #888423.
app-portage/flaggie

So I will deeply miss flaggie! Despite some issues it is a very
helpful thing once you know it, e.g. for automated USE flag changes
over ssh in a server farm.

I am rather in C than in python so I cannot really help advancing
flaggie. But I wonder whether there is a full specification for USE
in make.conf as well as for package.use/* so there was a chance to
think about a reimplementation somehow.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 2022-12-25 at 18:02 +0000, m1027 wrote:

mgorny:

# Michał Górny <mgorny@gentoo.org> (2022-12-25)
# make.conf writing is broken and package.use support incomplete.
# Last release in 2013.  Attempted unsuccessfully fixing it in 2017.
# Use an editor instead.
# Removal on 2023-01-24.  Bug #888423.
app-portage/flaggie

So I will deeply miss flaggie! Despite some issues it is a very
helpful thing once you know it, e.g. for automated USE flag changes
over ssh in a server farm.

Hmm, that's a use case I didn't think of (and I didn't know anyone is
actually using flaggie non-interactively). I guess most of the time you
could get away with something like:

echo app-foo/bar baz >> /etc/portage/package.use/local.conf

etc.

I am rather in C than in python so I cannot really help advancing
flaggie. But I wonder whether there is a full specification for USE
in make.conf as well as for package.use/* so there was a chance to
think about a reimplementation somehow.

To be honest, I'm thinking of starting from scratch like all cool
programmers do these days. Perhaps I should aim for a very simple tool
that doesn't try to represent all Portage configuration in AST
and instead just does plain manipulations. So perhaps they'll
be a flaggie2 after all.

--
Best regards,
Michał Górny

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

ajak:

On Sun, Dec 25, 2022 at 06:02:11PM +0000, m1027 wrote:

mgorny:

# Michał Górny <mgorny@gentoo.org> (2022-12-25)
# make.conf writing is broken and package.use support incomplete.
# Last release in 2013.  Attempted unsuccessfully fixing it in 2017.
# Use an editor instead.
# Removal on 2023-01-24.  Bug #888423.
app-portage/flaggie

So I will deeply miss flaggie! Despite some issues it is a very
helpful thing once you know it, e.g. for automated USE flag changes
over ssh in a server farm.

If you're doing configuration management over ssh, you might want a
proper configuration management solution anyway, like ansible or
puppet.

Yeah, I had a look on those some time ago. But how would you teach
those tools to understand and manipulate USE flags properly? That's
where flaggie is again required for AFAIK.

Well, I never got a fan of ansible & co and instead have my bunch of
bash scripts being sent/executed over ssh, opening tmux windows and
such. Tested for up to 30 Gentoo boxes and that just WFM.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Dec 25, 2022 at 06:02:11PM +0000, m1027 wrote:

mgorny:

# Michał Górny <mgorny@gentoo.org> (2022-12-25)
# make.conf writing is broken and package.use support incomplete.
# Last release in 2013.  Attempted unsuccessfully fixing it in 2017.
# Use an editor instead.
# Removal on 2023-01-24.  Bug #888423.
app-portage/flaggie

So I will deeply miss flaggie! Despite some issues it is a very
helpful thing once you know it, e.g. for automated USE flag changes
over ssh in a server farm.

If you're doing configuration management over ssh, you might want a
proper configuration management solution anyway, like ansible or
puppet.

I am rather in C than in python so I cannot really help advancing
flaggie. But I wonder whether there is a full specification for USE
in make.conf as well as for package.use/* so there was a chance to
think about a reimplementation somehow.

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQQyG9yfCrmO0LPSdG2gXq2+aa/JtQUCY6nkKwAKCRCgXq2+aa/J tXb3AQDhoFPdjOS22FC5YdyTgJU4I3QUheJJYA9lq6OoqjodugEAoJLXtCTWPqvN Jewm+pHJ68f/IMtOzxf9GA084wEmbAY=
=BW0Y
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

So I will deeply miss flaggie! Despite some issues it is a very
helpful thing once you know it, e.g. for automated USE flag changes
over ssh in a server farm.

Hmm, that's a use case I didn't think of (and I didn't know anyone is actually using flaggie non-interactively). I guess most of the time you could get away with something like:

echo app-foo/bar baz >> /etc/portage/package.use/local.conf

etc.

Yeah but... flaggie interprets all such files and it is able to keep
them clean by just editing it at the right place (well, mostly)
instead of having the same package being tweaked at mutiple places
back and forth again.

To be honest, I'm thinking of starting from scratch like all cool
programmers do these days. Perhaps I should aim for a very simple tool
that doesn't try to represent all Portage configuration in AST
and instead just does plain manipulations. So perhaps they'll
be a flaggie2 after all.

Oh, yes, please. "Just" something that does the monkey work of
such flag manipulations.

BTW: I'd really love to keep flaggie until there is your cool new
flaggie2 and I'm very willing to ignore my bug report: https://bugs.gentoo.org/746542

;-)

Thanks

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)