On Wed, 10 Feb 2016 11:36:23 Hans-Christoph Steiner wrote:
> Seems to me that if y'all don't want to add an alternatives setup, then
> we'll just do a Conflicts. All of the Android docs and tools just
> reference 'dx' so not providing 'dx' is not an option. Plus in my 35
> years of using computer
Seems to me that if y'all don't want to add an alternatives setup, then
we'll just do a Conflicts. All of the Android docs and tools just
reference 'dx' so not providing 'dx' is not an option. Plus in my 35
years of using computers in dotcom startups, media and art, psychiatry,
mobile and deskto
I agree with Graham, this is a plain and simple naming clash. The only
reasonable resolution is to rename one (or both) of the binaries.
You could workaround the clash with Conflicts:, but that's not
reasonable either since there's no reason both binaries shouldn't
coexists.
A possible alterna
Hi Hans-Christoph
On 8 February 2016 at 21:25, Hans-Christoph Steiner wrote:
> We have just packaged the "Dalvik Explorer" aka android-platform-dalvik
> which is always used as the command util 'dx'.
Always? IBM's DX has been around since 1991. :)
> This conflicts with
> OpenDX's /usr/bin/dx,
Package: dx
Version: 1:4.4.4-8
Severity: wishlist
We have just packaged the "Dalvik Explorer" aka android-platform-dalvik
which is always used as the command util 'dx'. This conflicts with
OpenDX's /usr/bin/dx, so I propose that OpenDX support /usr/bin/dx using
the 'alternatives' system. To do
