On 01/20/2015 12:03 AM, Sven Kieske wrote:
-----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:
- it complicates development a _lot_
- 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).
What about an use-case where Xen would be used with Storage SIG i.e. GlusterFS or Ceph or OpenAFS? Also Ovirt can be used for management of GlusterFS.
- 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).
Honestly I don't want to complicate stuff but just concerned that user does not face these kind of issues when he tries to use multiple SIGs.
-Lala
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----- _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel