Hi, I tested the latest compose of F21 Workstation and found out that dnf-plugins-core was not included in the default installation.
IMHO it's something we should fix. The package includes plugins that allow users to easily work with Copr repositories and the planned Playground repository. It should be part of the default user experience because it's one of the nice details and integration with our services. Copr has proven to be useful for both us (to give early adopters software they can test, e.g. GNOME 3.12 in F20) and users (to easily get new software which is not included in the official repositories yet) and we should make working with it as easy as possible.
For those who don't know it: with this plugin you can easily add/remove Copr repositores just by "dnf enable/disable name/project" instead of inconvenient copying/deleting repo files.
I know that DNF is not yet the default package manager, but many users already use it instead of yum just for these kind of things, so let's give them the full experience of DNF.
An impact on the image size is minimal. The total size of dnf-plugins-core including all its dependencies is 151 kB.
Jiri
On Wed, Oct 29, 2014 at 11:42 AM, Jiri Eischmann eischmann@redhat.com wrote:
Hi, I tested the latest compose of F21 Workstation and found out that dnf-plugins-core was not included in the default installation.
IMHO it's something we should fix. The package includes plugins that allow users to easily work with Copr repositories and the planned Playground repository. It should be part of the default user experience because it's one of the nice details and integration with our services. Copr has proven to be useful for both us (to give early adopters software they can test, e.g. GNOME 3.12 in F20) and users (to easily get new software which is not included in the official repositories yet) and we should make working with it as easy as possible.
For those who don't know it: with this plugin you can easily add/remove Copr repositores just by "dnf enable/disable name/project" instead of inconvenient copying/deleting repo files.
I know that DNF is not yet the default package manager, but many users already use it instead of yum just for these kind of things, so let's give them the full experience of DNF.
An impact on the image size is minimal. The total size of dnf-plugins-core including all its dependencies is 151 kB.
I'd be OK with this.
josh
On Wed, 2014-10-29 at 16:42 +0100, Jiri Eischmann wrote:
Hi, I tested the latest compose of F21 Workstation and found out that dnf-plugins-core was not included in the default installation.
IMHO it's something we should fix. The package includes plugins that allow users to easily work with Copr repositories and the planned Playground repository. It should be part of the default user experience because it's one of the nice details and integration with our services. Copr has proven to be useful for both us (to give early adopters software they can test, e.g. GNOME 3.12 in F20) and users (to easily get new software which is not included in the official repositories yet) and we should make working with it as easy as possible.
Including the plugins sounds ok to me. But maybe devassistant should offer to set these things up too ? 'Push my project to a Fedora Copr' sounds like a nice thing it could offer.
Matthias Clasen píše v St 29. 10. 2014 v 12:51 -0400:
On Wed, 2014-10-29 at 16:42 +0100, Jiri Eischmann wrote:
Hi, I tested the latest compose of F21 Workstation and found out that dnf-plugins-core was not included in the default installation.
IMHO it's something we should fix. The package includes plugins that allow users to easily work with Copr repositories and the planned Playground repository. It should be part of the default user experience because it's one of the nice details and integration with our services. Copr has proven to be useful for both us (to give early adopters software they can test, e.g. GNOME 3.12 in F20) and users (to easily get new software which is not included in the official repositories yet) and we should make working with it as easy as possible.
Including the plugins sounds ok to me. But maybe devassistant should offer to set these things up too ? 'Push my project to a Fedora Copr' sounds like a nice thing it could offer.
This may not be so much work afaik because DevAssistant can already generate RPMs from certain projects. On the other hand, I heard that the priority for DevAssistant guys is now integration with Docker which may, in the end, be the preferred means of distribution of projects in DevAssistant. I'm CC'ing Slavek Kabrda of the DevAssistant team to let him share his thoughts on this with us.
Jiri
On Wed, 2014-10-29 at 18:21 +0100, Jiri Eischmann wrote:
Including the plugins sounds ok to me. But maybe devassistant should offer to set these things up too ? 'Push my project to a Fedora Copr' sounds like a nice thing it could offer.
This may not be so much work afaik because DevAssistant can already generate RPMs from certain projects. On the other hand, I heard that the priority for DevAssistant guys is now integration with Docker which may, in the end, be the preferred means of distribution of projects in DevAssistant. I'm CC'ing Slavek Kabrda of the DevAssistant team to let him share his thoughts on this with us.
Docker is certainly useful for some things. But the way it is currently oversold as the solution to everything and anything is a bit scary...
desktop@lists.stg.fedoraproject.org
-
Jiri Eischmann -
Josh Boyer -
Matthias Clasen