https://bugzilla.rpmfusion.org/show_bug.cgi?id=3152
--- Comment #57 from Nicolas Chauvet <kwizart(a)gmail.com> 2014-04-13 14:57:16 CEST
---
Hi , I still don't understand how thing works, Why the dropbox-repo-config is
completely commented ? It would only be needed to have it enabled=0 so it would
make sense to install it and enable it as needed from command line:
yum install nautilus-dropbox --enablerepo=dropbox.
%triggerin -- nautilus-dropbox
cp /usr/share/system-config-repo/repos/%{reponame}/dropbox.repo \
/etc/yum.repos.d/%{reponame}.repo
This is insane ! if nautilus-dropbox is installed, why to overwrite the repo
file in the back of the user ? This is not acceptable at all. What if users
wants to have it disabled by default ?
Also the icon isn't available from the dropbox-repo.desktop file. I don't know
which package provide the scr-repo icon. the desktop file doesn't open the
dropbox.repo from the right path, it need to be explicitly set to
/etc/yum.repos.d/dropbox.repo
In the current shape of the package, why do you think it's needed to split the
dropbox-repo and dropbox-repo-config at all ?
I'm still holding the review, until this is fixed.
I was also wondering for the long term that /usr/share/appdata files would be
provided as yum metadata instead of using a package. Is it possible to go that
route instead of having one repo package for each 3rd part repository ?
An alternate way would be to provide them all in the related
rpmfusion-free-contrib-repo and rpmfusion-nonfree-contrib-repo instead.
My point of view is that if a dropbox-repo package exists, it needs to be
provided from
dropbox.com, (like adobe-x86_64-release or else).
Then as we don't want to duplicate content, the aim would be to only provide
the needed info from yum metadata to PackageKit that will discover then from
where to download theses adobe-*-release rpm package or .repo files along this
the description of each 3rd part repositories.
--
Configure bugmail:
https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.