Donnie Berkholz wrote:
> On 09:55 Wed 16 Apr , Tiziano Müller wrote:
>> What do the new ebuilds offer:
>> a) A split into dev-db/postgresql-{base,server,docs}. Now, I know that
>> splitting up packages isn't the Gentoo way. I know we could have done it
>> using USE flags but this approach gives more flexibility due to the
>> current way how binary packages are being generated and distributed.
>
> I'd like to hear some more info on this point.
Consider this use case:
30 machines with one staging machine and binary deployment.
On 28 machines you want the libraries only, on one you also need the server
and on one you want the docs.
Easy done with (sanely) splitted packages.
Please note that the only additional package compared to the split
dev-db/{libpq,postgresql} is dev-db/postgresql-docs.
>
>> In general the only thing you have to then do is to uninstall
>> dev-db/libpq and dev-db/postgresql and install the same version of
>> postgresql-base and postgresql-server. No revdep-rebuild is needed.
>> For early adopters: It's best to wait until we changed the dependencies,
>> afterwards you can unmask the dev-db/postgresql-{docs,base,server}
>> packages...
>
> People want `emerge postgresql` to do something. Otherwise it's not
> always obvious which random hyphenated packages you're supposed to
> install, and it's just like you're digging around some huge subpackage
> list in Ubuntu or Fedora.
Well, we can re-introduce a virtual/postgresql (or dev-db/postgresql) after
the old ebuilds are gone.
Cheers,
Tiziano
--
gentoo-dev@lists.gentoo.org mailing list
