-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Diego 'Flameeyes' Petten� wrote: | Another useflag-related question. | | Currently, the encode useflag is defined as follow: | | encode - Adds support for MEncoder or LaME encoder, wherever applicable | | this is a loose definition which is quite useless for medium user, as it's | used also in a non-complete-standard way in all ebuilds. | | My proposal is to start using lame useflag to enable lame support (in software | which is just encoding on itself), and using encode with a slight different | definition for example: | | encode - Adds support for encoding files in addiction to decoding
should this be ok'ed make sure to put addition, not addiction | | so that it can be used to enable generic encoding support instead of specific | using lame or mencoder. | | Comments?
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFChuvPUpKYMelfdYERAm5XAJ0QKEhbGcBiPju0RWYoDDIeU4NNsQCfby8l Hy1CnYNhXUTkeOT5t8ZoelE= =wYmu -----END PGP SIGNATURE----- -- [email protected] mailing list
