public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] encode useflag
Date: Thu, 12 May 2005 11:12:44 +0200	[thread overview]
Message-ID: <200505121112.58254@enterprise.flameeyes.is-a-geek.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

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

so that it can be used to enable generic encoding support instead of specific 
using lame or mencoder.

Comments?
-- 
Diego "Flameeyes" Pettenò
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)

http://dev.gentoo.org/~flameeyes/


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-05-12  9:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12  9:12 Diego 'Flameeyes' Pettenò [this message]
2005-05-12 12:35 ` [gentoo-dev] encode useflag Mike Frysinger
2005-05-12 15:52   ` Simon Stelling
2005-05-12 16:18     ` Mike Frysinger
2005-05-12 16:50       ` Diego 'Flameeyes' Pettenò
2005-05-12 17:02         ` Mike Frysinger
2005-05-12 17:19           ` Matthijs van der Vleuten
2005-05-12 18:03             ` Mike Frysinger
2005-05-12 18:55               ` Simon Stelling
2005-05-12 19:20                 ` Gregorio Guidi
2005-05-12 19:22                   ` Diego 'Flameeyes' Pettenò
2005-05-12 19:48                     ` Gregorio Guidi
2005-05-13 11:19                       ` Luca Barbato
2005-05-12 12:40 ` Brian Jackson
2005-05-15  6:27 ` Daniel Goller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200505121112.58254@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox