Re: bat: naming conflict in distribution packages with Bareos/Bacula

[Liam Girdwood <liam.r.girdwood@linux.intel.com>]

On Mon, 2016-01-11 at 16:07 +0100, Takashi Iwai wrote:
> Hi,
> 
> sorry for the late response, as this post buried behind many Christmas
> tree decorations...

Sorry, didn't see this either....

> 
> On Wed, 23 Dec 2015 12:59:55 +0100,
> J6rg Steffens wrote:
> > 
> > 
> > Hello,
> > 
> > my name is Jörg Steffens and I'm one of the maintainers of the Bareos
> > backup software project. Bareos is a fork Bacula.
> > 
> > Bareos includes a GUI program called bat (bareos administration tool).
> > bat have been around since 2007.
> > 
> > alsa-utils as well as bareos-bat (as well a some Bacula packages) all
> > contain a program called /usr/bin/bat, which causes conflicts on various
> > distributions ("basic audio tester" vs "bareos administration tool"
> > ("bacula administration tool")).
> > See http://pkgs.org/search//usr/bin/bat
> > 
> > We received a bug report/feature request
> > https://bugs.bareos.org/view.php?id=576 from Michel, the maintainer of
> > Bareos for Arch Linux about how to solve the naming conflict with we
> > latest ALSA 1.1.0.
> > 
> > I wanted to raise the question, if you are aware of this potential
> > problem? Maybe you have guidelines for package maintainers how to solve
> > this.
> > Some distributions have separated "basic audio tester" from the
> > alsa-utils package, like Fedora with alsa-utils-bat.
> > I think, this will work out well, as I assume "basic audio tester" is
> > not stricly required on all systems. "bareos administration tool" at
> > least is optional and typical installed on administrative workstations.
> 
> It's bad to have such a naming conflict, indeed.  This wasn't
> intentional, of course.

It certainly wasn't, I did check for collisions on a few distros but
none of then had Bareos installed.

> 
> I, as one of maintainers, am neutral about renaming: if other people
> prefer keeping this, I'd say simply to push this to each distro
> packager.  How to solve such an issue pretty depends on the
> distribution.  And they (must) know well such a case.
> 
> OTOH, if we all agree with renaming to something less likely
> conflicting, I'm all fine with it.  It's a new program, so not too
> much impact yet by a rename, I suppose.
> 
> Let's first ask Intel people who are the author of our BAT.
> 

What about prefixing "alsa" or "a" to to bat ? We already have
alsamixer, aplay, alsactl....

Thanks

Liam

> 
> thanks,
> 
> Takashi


_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel