| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Diego 'Flameeyes' Pettenò wrote: |
| 5 |
| Another useflag-related question. |
| 6 |
| |
| 7 |
| Currently, the encode useflag is defined as follow: |
| 8 |
| |
| 9 |
| encode - Adds support for MEncoder or LaME encoder, wherever applicable |
| 10 |
| |
| 11 |
| this is a loose definition which is quite useless for medium user, as |
| 12 |
it's |
| 13 |
| used also in a non-complete-standard way in all ebuilds. |
| 14 |
| |
| 15 |
| My proposal is to start using lame useflag to enable lame support (in |
| 16 |
software |
| 17 |
| which is just encoding on itself), and using encode with a slight |
| 18 |
different |
| 19 |
| definition for example: |
| 20 |
| |
| 21 |
| encode - Adds support for encoding files in addiction to decoding |
| 22 |
|
| 23 |
should this be ok'ed make sure to put addition, not addiction |
| 24 |
| |
| 25 |
| so that it can be used to enable generic encoding support instead of |
| 26 |
specific |
| 27 |
| using lame or mencoder. |
| 28 |
| |
| 29 |
| Comments? |
| 30 |
|
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 33 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 34 |
|
| 35 |
iD8DBQFChuvPUpKYMelfdYERAm5XAJ0QKEhbGcBiPju0RWYoDDIeU4NNsQCfby8l |
| 36 |
Hy1CnYNhXUTkeOT5t8ZoelE= |
| 37 |
=wYmu |
| 38 |
-----END PGP SIGNATURE----- |
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives