public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] splitting one source package into many binaries
Date: Thu, 16 Jun 2005 19:05:16 +0200	[thread overview]
Message-ID: <1118941516.3331.13.camel@localhost> (raw)
In-Reply-To: <564d96fb0506160950b9752bf@mail.gmail.com>

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

On Thu, 2005-06-16 at 13:50 -0300, Rafael Espíndola wrote:
> I am using Gentoo to build some small systems. While things like the
> minimal useflag is a joy, the monolithic nature of most gentoo
> packages is a headache.
It depends on your point of view.
Having to install 142 -devel packages just to be able to compile $foo is
quite frustrating - I prefer the Gentoo way.

> Kde has been spit and libstdc++ can be installed without gcc but there
> are many other packages that don't have this feature. For example,
> installing qt also installs qt designer.
I don't know if there is a demand for this, but if you really need to
shrink stuff, create your own ebuild overlay with "fixed" ebuilds ...
> Has someone worked on changing ebuild so that it could create many
> binary packages from one source? Something similar to debian's
> dpkg-buildpackage. For example, it would be wonderful to be able to do
> 
> ebuild qt-something.ebuild split-package
I haven't heard of anyone trying this, and as far as I can remember it has usually been shot down as a bad idea.
> and have in /usr/portage/packages a package for qt-designer and a
> package for the rest of the library.
> 
> Is this a bad idea or simply not the Gentoo way?
Well ... it gets you all kinds of problems because if you split packages
(e.g. X --> X + X-headers) and you want to compile something you'll pull
in the second package anyway. So for most packages I think it's not
really useful.

wkr,
Patrick
-- 
Stand still, and let the rest of the universe move

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2005-06-16 17:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 16:50 [gentoo-dev] splitting one source package into many binaries Rafael Espíndola
2005-06-16 17:01 ` Caleb Tennis
2005-06-16 22:35   ` Rafael Ávila de Espíndola
2005-06-16 17:05 ` Patrick Lauer [this message]
2005-06-16 22:51   ` Rafael Ávila de Espíndola
2005-06-17  8:10     ` [gentoo-dev] " Duncan
2005-06-21  5:47       ` Donnie Berkholz
2005-06-16 17:20 ` [gentoo-dev] " Mike Frysinger
2005-06-16 17:40 ` Brian Jackson
2005-06-16 18:20   ` Yuri Vasilevski
2005-06-17  8:21     ` [gentoo-dev] " Duncan
2005-06-17 10:03       ` Jon Portnoy
2005-06-17 13:56       ` Chris Gianelloni
2005-06-18 12:17         ` [gentoo-dev] " Duncan
2005-06-20 15:39           ` Chris Gianelloni
2005-06-21  2:10             ` [gentoo-dev] " Duncan
2005-06-17 10:56 ` [gentoo-dev] " Thomas de Grenier de Latour
2005-06-17 14:21   ` Brian Jackson

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=1118941516.3331.13.camel@localhost \
    --to=patrick@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