[gentoo-dev] Re: lame use flag, local to global
Chris Gianelloni [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Fri, 12 Oct 2007 17:22:54 -0700: Steve Long wrote: Duncan wrote: Steve Dibb posted: there is more than one mp3 encoder. [S]houldn't the description mention that? How about: Prefer using LAME for MP3 encoding support It doesn't mention anything else, so it'll work in all cases. WORKSFORME =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: lame use flag, local to global
On Sat, 2007-10-13 at 10:37 +, Duncan wrote: Chris Gianelloni [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Fri, 12 Oct 2007 17:22:54 -0700: Steve Long wrote: Duncan wrote: Steve Dibb posted: there is more than one mp3 encoder. [S]houldn't the description mention that? How about: Prefer using LAME for MP3 encoding support It doesn't mention anything else, so it'll work in all cases. WORKSFORME =8^) InCVS... :P I've gone ahead and changed this. It isn't a harmful change, so I just went ahead and did it. Enjoy your newly modified description. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
[gentoo-dev] Re: lame use flag, local to global
Duncan wrote: Steve Dibb [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600: The reason we have mp3 and lame use flag is because there is more than one mp3 encoder. In almost every case of the use flag being applied above, there is already support for another mp3 codec (ffmpeg). So, lame adds support for lame, not for mp3, which is also provided. In that case, shouldn't the description mention that? Something like: MP3 encoding support using LAME (as opposed to ffmpeg) What about when the next one gets added-- would it need to say as opposed to ffmpeg or lame? I agree where there's a choice, the ebuild should offer lame or ffmpeg or w/e, and where not simply mp3 (along with the encode/decode being orthogonal.) -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Re: lame use flag, local to global
Steve Long [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Fri, 12 Oct 2007 07:26:12 +0100: In that case, shouldn't the description mention that? Something like: MP3 encoding support using LAME (as opposed to ffmpeg) What about when the next one gets added-- would it need to say as opposed to ffmpeg or lame? Good point. However, my minor complaint with USE flags is that they too often don't really say what the USE flag actually does. In this case as- is, the implication is that with -lame, there's no encoding support, when the general case is that there's still encoding support, but from something else (ffmpeg). Ideally, the description isn't so vague as to leave the user with the wrong impression, or having to dig into the ebuild itself to find out what the practical effect is. So something like: Support LAME as mp3 encoder (see ffmpeg also) Then ideally, if a package supported both encoders, both would be flags, and if possible, support for both would be built if both USE flags were enabled. That's a bit more expandable, altho it still mentions ffmpeg. Making it generic (other encoders may also be supported) might be better in some ways, but isn't as helpful in others. IMO, the ffmpeg reference is more helpful, and the mention of ffmpeg could be expanded if other options become popular enough to warrant it. What I'd /really/ like would be a simple way to list what each flag does in a particular package, sort of like what use.local sometimes does now, if the description is specific enough, but for global flags as well. Take USE=perl. Sure, it supports perl, but is it perl bindings, or additional user scripts in perl, or documentation for perl devs, or ??? A use.local.desc (or whatever) file listing every package with the flag, and what the flag actually does in that package in practical terms, would sure be useful! =8^) Of course, being a separate file, it'd be difficult to keep up to date. Perhaps a better solution might be an IUSE_DESC variable that every ebuild and eclass could (and would eventually be required to) populate. Then it's metadata for the package kept right in the ebuild/eclass, where it's easy to keep up to date when the package itself changes. Then all we'd need would be a parsing tool for that info... euse could be expanded to grab it if --verbose is set, perhaps, and life would be /so/ much easier, at least for /some/ users. =8^) Yes, I know the chances of it happening would be better if I were to become a dev and volunteer to help with all the updates, since it's my itch I want scratched. Maybe it'll happen someday. In the mean time... maybe I can spread the itch. =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: lame use flag, local to global
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Long wrote: Duncan wrote: Steve Dibb [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600: The reason we have mp3 and lame use flag is because there is more than one mp3 encoder. In almost every case of the use flag being applied above, there is already support for another mp3 codec (ffmpeg). So, lame adds support for lame, not for mp3, which is also provided. In that case, shouldn't the description mention that? Something like: MP3 encoding support using LAME (as opposed to ffmpeg) What about when the next one gets added-- would it need to say as opposed to ffmpeg or lame? I agree where there's a choice, the ebuild should offer lame or ffmpeg or w/e, and where not simply mp3 (along with the encode/decode being orthogonal.) what about mp3=lame or mp3=ffmpeg? This will also be easily extendable when the next implementations comes along (mp3=newmp3lib). Marijn - -- Marijn Schouten (hkBst), Gentoo Lisp project http://www.gentoo.org/proj/en/lisp/, #gentoo-lisp on FreeNode -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHD03xp/VmCx0OL2wRAgIxAJ47l1Y0IdL3n/GGKPYoiYW2Ec/IAwCeIDxp mNGh5idhB7qUVEDQb3Y65sI= =dwdN -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Re: lame use flag, local to global
Marijn Schouten (hkBst) [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Fri, 12 Oct 2007 12:35:30 +0200: what about mp3=lame or mp3=ffmpeg? This will also be easily extendable when the next implementations comes along (mp3=newmp3lib). I gotta admit... I didn't quite understand the practical effect of that N- way USE flag thing until now, maybe 'cause I was rather sleep deprived when I was trying to make sense of it, but this example even *I* can understand! =8^) IOW, thanks. =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: lame use flag, local to global
On Fri, 2007-10-12 at 07:26 +0100, Steve Long wrote: Duncan wrote: Steve Dibb [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600: The reason we have mp3 and lame use flag is because there is more than one mp3 encoder. In almost every case of the use flag being applied above, there is already support for another mp3 codec (ffmpeg). So, lame adds support for lame, not for mp3, which is also provided. In that case, shouldn't the description mention that? Something like: MP3 encoding support using LAME (as opposed to ffmpeg) What about when the next one gets added-- would it need to say as opposed to ffmpeg or lame? I agree where there's a choice, the ebuild should offer lame or ffmpeg or w/e, and where not simply mp3 (along with the encode/decode being orthogonal.) How about: Prefer using LAME for MP3 encoding support It doesn't mention anything else, so it'll work in all cases. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
[gentoo-dev] Re: lame use flag, local to global
Steve Dibb [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600: The reason we have mp3 and lame use flag is because there is more than one mp3 encoder. In almost every case of the use flag being applied above, there is already support for another mp3 codec (ffmpeg). So, lame adds support for lame, not for mp3, which is also provided. In that case, shouldn't the description mention that? Something like: MP3 encoding support using LAME (as opposed to ffmpeg) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
