#4944: Please mark sane-backends-drivers-{cameras, scanners} multiarch from F-14 on
Fedora Release Engineering
rel-eng at fedoraproject.org
Thu Oct 6 08:14:19 UTC 2011
#4944: Please mark sane-backends-drivers-{cameras,scanners} multiarch from F-14 on
-----------------------+----------------------------------------------------
Reporter: nphilipp | Owner: rel-eng at lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: mash
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment (by nphilipp):
Replying to [comment:4 rdieter]:
> i've several concerns about this update splitting drivers out :
>
> * for < f16, this changes how multilib'ing is done mid-release.
problems being though, the spilt package has already gone stable and the
damage done. One remedy (at least in the short-term), I'd encourage you
to add a hard deps to pre-f16 -libs subpkg:
> {{{
> Requires: %{name}-backends-drivers-cameras%{?_isa} =
%{version}-%{release}
> Requires: %{name}-backends-drivers-scanners%{?_isa} =
%{version}-%{release}
> }}}
If it's all the same, I'd rather add these deps to the -devel subpackage,
so the spins in question nave a benefit.
> * for f16+ (echo'd from bz): Realize now sane-backends (and apps using
it) doesn't "just work", how are these -driver-* subpkgs ever to be
installed? are they pulled in via comps somehow or users are now expected
to manually install drivers? and, comparing to cups isn't exactly fair,
cups includes pk integration to pull in needed drivers on demand... (or is
sane-backends able to do something like that?)
They are pulled in via comps, I've added them as default packages for
groups which should have scanners working (graphics, design suite).
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4944#comment:6>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
More information about the rel-eng
mailing list