From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for advanced useflag-syntax
Date: Fri, 4 Aug 2006 02:01:30 -0700 [thread overview]
Message-ID: <20060804090130.GA15814@seldon> (raw)
In-Reply-To: <44D2FD2A.6080505@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Fri, Aug 04, 2006 at 09:54:18AM +0200, Simon Stelling wrote:
> Enrico Weigelt wrote:
> >For example: mplayer
> >It has it's gui-less player and an gtk-based frontend in one package.
> >We should split this into two packages: mplayer and gmplayer.
> >The chances to get this done in the upstream *before* some major
> >distro like gentoo does the split by its own are quite low.
>
> Not quite true. In reality, they're just the same. mplayer simply checks
> whether it was called as mplayer or gmplayer. So you not only have two
> programs in one package, but even in one binary. Changing this behaviour
> has nothing to do with packaging and is really upstream's responsibility,
> IMHO.
Additionally... once you start down that path, the changes to pkgs
become less then minor. Some are simple, some ain't.
Personally, I hate that approach- ignoring any political/warring
idiocy, my main issue with debian is the choice to split upstream
packages into multiple sub packages. Makes things a pain in the ass
to what you want/need and makes for fun lock-step dependencies between
the subpackages.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-04 9:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 11:31 [gentoo-dev] Proposal for advanced useflag-syntax Noack, Sebastian
[not found] ` <20060803153407.GA19696@nibiru.local>
2006-08-03 18:38 ` Luca Barbato
[not found] ` <20060807131642.GF25236@nibiru.local>
2006-08-07 13:40 ` Paul de Vrieze
2006-08-07 14:18 ` Enrico Weigelt
2006-08-07 10:58 ` Alec Warner
2006-08-07 16:40 ` [gentoo-dev] " Duncan
2006-08-07 21:08 ` [gentoo-dev] " Paul de Vrieze
2006-08-08 10:30 ` Enrico Weigelt
2006-08-08 10:39 ` Simon Stelling
2006-08-08 10:58 ` Enrico Weigelt
2006-08-08 10:57 ` Jakub Moc
2006-08-04 7:54 ` Simon Stelling
2006-08-04 9:01 ` Brian Harring [this message]
2006-08-07 13:48 ` Enrico Weigelt
2006-08-07 14:08 ` Stephen P. Becker
2006-08-08 1:44 ` W.Kenworthy
2006-08-08 2:14 ` Mike Frysinger
2006-08-08 10:34 ` Enrico Weigelt
2006-08-08 2:50 ` Donnie Berkholz
2006-08-08 10:40 ` Enrico Weigelt
2006-08-08 12:37 ` Jan Kundrat
2006-08-08 14:50 ` Enrico Weigelt
2006-08-08 15:06 ` Lance Albertson
2006-08-08 20:17 ` Enrico Weigelt
2006-08-08 20:37 ` Lance Albertson
2006-08-08 20:46 ` Jan Kundrát
2006-08-08 21:22 ` Curtis Napier
2006-08-08 15:12 ` Thomas Cort
2006-08-08 20:22 ` Enrico Weigelt
2006-08-08 21:02 ` Richard Fish
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 6:21 AW: " Noack, Sebastian
2006-08-07 13:26 ` Enrico Weigelt
2006-08-07 14:53 ` Thomas Cort
2006-08-07 18:48 ` Enrico Weigelt
2006-08-07 20:09 ` Marius Mauch
2006-08-07 21:14 ` Paul de Vrieze
2006-08-07 15:04 AW: " Noack, Sebastian
2006-08-07 20:18 ` Enrico Weigelt
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=20060804090130.GA15814@seldon \
--to=ferringb@gmail.com \
--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