On Mon, 2008-09-29 at 10:17 -0430, Patrick O'Callaghan wrote:
On Mon, 2008-09-29 at 16:28 +0300, Gilboa Davara wrote:
> On Mon, 2008-09-29 at 12:22 +0200, MartinG wrote:
> > On Thu, Sep 25, 2008 at 6:24 PM, Gilboa Davara <gilboad(a)gmail.com>
wrote:
> > > kdebluetooth4 has just been pushed to update testing.
> > > While missing a number of major features compared to its KDE 3.5.x
> > > version (notably ioslaves integration) - it should be far more stable.
> >
> > I can't seem to find it, am I doing anything wrong here..?:
> > # yum --enablerepo=rawhide,updates-testing-newkey install kdebluetooth4
> > ...
> > No package kdebluetooth4 available.
> > Nothing to do
> >
> > Also, seems that I've got the old package twice:
> > # rpm -qa kdeblue\*
> > kdebluetooth-1.0-0.43.beta8.fc10.i386
> > kdebluetooth-libs-1.0-0.43.beta8.fc10.i386
> > kdebluetooth-libs-1.0-0.41.beta8.fc9.i386
> >
> > Maybe something got messed up in the transition to rawhide...
> > Any tips on how to clean things up appreciated!
> >
> > -MartinG
> > (kernel 2.6.27-0.352.rc7.git1.fc10.i686)
> >
>
> To keep the noise down, it's still being called kdebluetooth.
For some values of "noise". The actual executables are called
kbluetooth4 etc. (*not* kdebluetooth4 or whatever). I don't remember if
it was always like that but it is a bit confusing. Some consistency in
this would be appreciated.
poc
If upstream calls the project kdebluetooth I cannot really call it
kbluetooth, can I.
For obvious reasons, upstream decided to name the KDE 4.x version of the
kdebluetooth kdebluetooth4; however, renaming the package under F9's
feet could have generated a lot of problems - hence, I decided to keep
the kdebluetooth name.
- Gilboa