OK. I misread the email then. I'd just call it what upstream is going to
call it then if Debian is willing to do the same. I agree it's inelegant, but
users will rarely see it since this will get installed primarily via
metapackage (I assume).
On Monday, March 02, 2015 11:32:00 PM Jonathan Riddell wrote:
> Debian haven't made a decision as it hasn't been packaged yet. The
> question for now is should we diverge from probable upstream naming.
> On 2 March 2015 at 22:45, Scott Kitterman <ubu...@kitterman.com> wrote:
> > I don't see a reason to diverge from Debian here.
> > Scott K
> > On Monday, March 02, 2015 08:24:26 PM Jonathan Riddell wrote:
> > > I'm packaging the Plasma 5 version of kdeconnect, I'd like to ask for a
> > FFe
> > > and any testers very welcome
> > > https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1427349
> > > ppa:jr/ppa install kdeconnect-plasma5
> > >
> > > Upstream releases the kdelibs4 version as kdeconnect-kde and plans to
> > > release the plasma 5 version as kdeconnect-plasma5. The naming is
> > > inelegant and debian have changed the source and binary to just
> > > kdeconnect. What should I name the plasma 5 version? It does overlap
> > and
> > > replace the kdelibs4 version in various ways but with be released with a
> > > different tar upstream.
> > >
> > > Jonathan
> > --
> > kubuntu-devel mailing list
> > kubuntu-de...@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel