[gentoo-dev] Last rites: dev-util/android-sdk-update-manager

2024-12-05 Thread Florian Schmaus

# Volkmar W. Pogatzki  (2024-12-04)
# Bugs #845294 #757543 #517744 #704198 #366739 #350302 #614318 #637422
# #738898 #501586.
# Blocks removal of dev-java/swt-3.7.2-r4, bug #944885.
# Users should switch to dev-util/android-sdk-cmdline-tools for a CLI
# replacement or dev-util/android-studio for a GUI replacement.
# Removal on 2025-01-04
dev-util/android-sdk-update-manager


OpenPGP_0x8CAC2A9678548E35.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


[gentoo-dev] [RFC] New global USE flag -- twolame

2024-12-05 Thread Filip Kobierski
Hello,
lately I have noticed that audacity can use twolame.
I have researched that flag and noticed that all 9 packages
listing it as a USE flag use media-sound/twolame.

I suggest adding twolame as a global USE flag with a description
used by media-libs/avidemux-plugins:
"Enable TwoLAME support via media-sound/twolame, an optimised MPEG Audio Layer 
2 (MP2) encoder."

I think it fits all the software uses perfectly, besides FFMPEG,
which right now points out that it is an alternative to an
internal encoder.
I think it only makes sense to have it be a global USE flag since
many packages use it.

What do you think about it?


Kind regards
Filip Kobierski

signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] [PATCH] profiles/default/linux: export cache variables for sed and friends

2024-12-05 Thread Michael Orlitzky
On 2024-12-04 22:55:22, Sam James wrote:
> Prompted by yet another instance of this, this time at
> https://forums.gentoo.org/viewtopic-t-1171999.html.
> 
> The results of these tests are often hardcoded into installed files
> which causes issues if using a binpkg of them from a merged-usr system
> on a non-merged-usr system. Just set the cache variables to avoid that.
> ...
> +ac_cv_path_SED="sed"

Obviously it would defeat the purpose to put a full path in there, but
won't this break software that expects them to be a path (since that's
what the autoconf macros are documented to do)?