[pkg-apparmor] Bug#742829: Bug#742829: Chromium browser profile not adapted to Debian packaging

[Christian Boltz]

Hello,

Am Montag, 19. Oktober 2015 schrieb Daniel Richard G.:
> I've never expected that we could get everyone to agree on a common
> set of paths, any more than we can get everyone to agree to drive on
> the same side of the road. But at least we can harmonize things
> between Debian and Ubuntu---there's little good reason for *that*
> inconsistency---
> and retool the Chromium profile to make it easy to deal with typical
> path variations like openSUSE's.

I know that the lib vs. lib64 difference will stay, but that doesn't 
mean that we should also keep other differences "because it's already 
different". Better have one difference than two ;-)
That's why I vote for using "chromium" and not "chromium-browser" ;-)

We can easily use /usr/lib{,64}/ in the profile (both name and content) 
without breaking something [1]. In theory, the profile could also use 
/usr/lib{,64}/chromium{,-browser}/chromium{,-browser} - but that's where 
things start to become ugly to read ;-)


Regards,

Christian Boltz

[1] Yes, that will allow the Debian chromium to access /usr/lib64/ - but
    since that directory doesn't exist, it won't hurt.
    BTW: The profiles in the upstream AppArmor tarball and several 
    abstractions already use /usr/lib{,64} a lot.
-- 
Opensuse-Factory is mainly for systemd infights and KDE3 legacy
maintainence questions nowadays. I guess you chose the right list ;-)
[Ralf Lang in opensuse-programming]