On 3 March 2014 11:08, olivier sallou <[email protected]> wrote:
> CC'ing the list > > > ---------- Forwarded message ---------- > From: olivier sallou <[email protected]> > Date: 2014-03-03 11:08 GMT+01:00 > Subject: opennebula plugin > To: Anders Ingemann <[email protected]> > > > Hi, > I have put opennebula context package in Debian and Wheezy backports. > This means, now, that to get opennebula support, all that will be needed > is to put the opennebula-context package in package list (from main or > backport). > > My question is, should we remove completly the opennebula plugin, or > should we keep it as a plugin that will just add the package from main or > backport depending on targeted release. > > User could add the package himself in manifest, but he has to know what to > add, and from which mirror/repo. > Keeping it as a plugin is a simpler task for the user. > > What do you think? > > Olivier > > -- > > gpg key id: 4096R/326D8438 (keyring.debian.org) > > Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 > > > > > -- > > gpg key id: 4096R/326D8438 (keyring.debian.org) > > Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 > > I'd go for the plugin. It's a one-off that is relevant for a meta-provider, I think that warrants a plugin which makes it easier for users.
