[CentOS-devel] SIG repo layout and conflicts between projects within a SIG

Mon Jan 19 18:33:00 UTC 2015
Sven Kieske <svenkieske at gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19.01.2015 13:40, Lalatendu Mohanty wrote:
> I like #1, even if it is more work. I think it is logical thing to
> do as SIGs should not conflict with each other when a user consumes
> them. I mean one of the purpose of SIGs to improve the user
> experience for consuming stuffs that are not present in CentOS
> core.

Being not a sig member but a user:

I dislike option 1 for several reasons:

1. it complicates development a _lot_
2. I can't imagine any usecase where you e.g.
want to mix xen-kernel with ovirt, as ovirt
has no xen support (yet), so those don't need
to be compatible (at least for now).
3. possibly adding more bloat:
in order to satisfy this one-repo-for-all
you might need to define some silly dependencies
(libvirt requiring xen-kernel, when you don't
need xen-kernel, but just ovirt/kvm).

kind regards

Sven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQGcBAEBAgAGBQJUvU3cAAoJEAq0kGAWDrqlIh8L/RM9NGbLIdYh1Mnfq/h0vCS1
bjWojMpiQUKaCxKsFjqAPtXSF6eXDXEiI8/Ymw9rMQMHY86WPzFltArf7hi/6phG
NBn77hPt0QBu+KukIEPa5X6tf/xhTwf0HQw6tGBni4ynSCQVFu+soE5EFshPBZiI
MpxEKlCJKUFMQVHXOkRQlr0bpvWN+eLWSBJ4k6bxW9SJsRsmXqWzhVhnurz/sCgx
N+cj1h2FIHC7F/gkwXwO24Q4CFe4ahbUBvtZbFZl4rWFg8ZbywN96qRRuLnRiUPS
hQH2YwvT4ojQL45uSp+4Z1vcyeGfyQzKY9k8yRVxg46vhfjKtNkPp6S7K2Vlg4o7
HGcXs1IhXLvP7RJvQaY1VHJ5Yg0br+wb6kjdbTggJrIZT7hyx7KFX68W/yA5ijmm
oGB9Jggo/oTMYOVDpMiczvs8guJMXPC2lSS72kZ6zQNJz2nbDDFZFdPHxupdqcfK
BWie6fyGv1Iu490VDwZy9pkrbPjW2NeLGbm/3dQk2Q==
=jjzb
-----END PGP SIGNATURE-----