#4944: Please mark sane-backends-drivers-{cameras, scanners} multiarch from F-14 on

[Fedora Release Engineering]

#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:8 notting]:
 > Replying to [comment:7 nphilipp]:
 > > Replying to [comment:6 nphilipp]:
 > > > If it's all the same, I'd rather add these deps to the -devel
 subpackage, so the spins in question nave a benefit.
 > >
 > > I've skimmed through mash code a bit, but while mash.multib knows many
 multilib methods, mash seems to me to only be able to employ one of them
 (Mash.config.multilib_method) at a time. So will making the -devel package
 depend on -drivers-* have the desired effect here?
 >
 > Yes.

 Good, I'll do that then.

 > > > They are pulled in via comps, I've added them as default packages
 for groups which should have scanners working (graphics, design suite).
 > >
 > > Are comps "consumers" (anaconda, PK, e.a.) supposed to cope with
 packages they don't find in the configured repositories? I'm looking at
 the case where something would work on an old repository (without
 -drivers-* packages), but have new comps data. If that is safe, I'd add
 these packages to old comps.xml as well.
 >
 > groupinstall, etc. will still 'work' if they can't find a package (yum
 groupinstall will likely print a warning)
 >
 > How are you handling upgrades - comps isn't used for that.

 Old packages are obsoleted by new ones. Basically if you had scanner
 drivers (subpackage -libs) before, you'll end up with -drivers-scanners
 being installed, if you had camera drivers (subpackage -libs-gphoto2),
 -drivers-cameras will be installed. The only way I can think of right now
 that'd leave you without drivers is if you selected individual packages in
 e.g. a kickstart installation (i.e. not upgrade), rather than going with
 groups and their default packages.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4944#comment:9>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project