public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-doc@lists.gentoo.org
Subject: [gentoo-doc] Re: Fwd: Gentoo Linux Bluetooth Guide
Date: Thu, 15 Jul 2010 15:12:01 +0100	[thread overview]
Message-ID: <87oce8hm1a.fsf@evenstar.local.lan> (raw)
In-Reply-To: AANLkTikxApq8ps-2BgsrONu-BwOko7WLJmzsxrrhEXfM@mail.gmail.com

Ioannis Aslanidis <deathwing00@gentoo.org> writes:

> FYI
>
>
> ---------- Forwarded message ----------
> From: Peter Gazi <gazi@dcs.fmph.uniba.sk>
[...]
> just a quick feedback to the Gentoo Linux Bluetooth Guide from a user:
>
> - currently there are no net-wireless/bluez-libs
> net-wireless/bluez-utils packages in my (stable) portage.

There was really a move to net-wireless/bluez, but as Josh Saddler said
in bug 286826 (#6), it's not just the same package under a different
name.

Some helper tools are gone (like passkey-agent). Same goes for daemons -
elog messages say hidd is now only built when USE="+old-daemons".

> - there is no kdebluetooth, it seems the package is called kbluetooth.

I'm not a kde user, so I can't help with this one.


There is already a bug about updating the bluetooth guide (286826, the
same I mentioned above), due to which it was marked as draft.

Revision 1.17 
Mon Jun 21 19:03:09 2010 UTC (3 weeks, 2 days ago) by nightmorph 
"mark as draft, until someone steps up and helps the GDP update the
guide. bug 286826."

> I just noticed these minor things while using your guide and thought
> this might help.
>
> Thanks for your work,
>
> Peter

-- 
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg




      reply	other threads:[~2010-07-15 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C3E4007.9010204@dcs.fmph.uniba.sk>
2010-07-15  7:48 ` [gentoo-doc] Fwd: Gentoo Linux Bluetooth Guide Ioannis Aslanidis
2010-07-15 14:12   ` Nuno J. Silva [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oce8hm1a.fsf@evenstar.local.lan \
    --to=nunojsilva@ist.utl.pt \
    --cc=gentoo-doc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox