public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] New libudev and libgudev virtual
Date: Sun, 30 Mar 2014 21:58:19 +0300	[thread overview]
Message-ID: <5338694B.2030004@gentoo.org> (raw)

I sent this mail earlier, but it was denied because of:

21:52 <antarus> Sat Mar 29 04:37:39 2014 mlmmj-process: access - A mail from "ssuominen@gentoo.org" was denied by rule #12 
"deny !^Reply-To:" because no header matched.

That is why you are reading this only now.

To the point:

There was a need for two new virtuals since udev has two libraries, each
with their own SONAMEs.
This is to get the benefits of automatic rebuilds to fix the breakage we
saw with libudev.so.0 going away a while ago.

You can now use:

virtual/udev (without :=, no libraries)
virtual/libgudev:= (with :=, for SONAME of libgudev-1.0.so.x)
virtual/libudev:= (with :=, for SONAME of libudev.so.x)

We have opened a Tracker bug 506034 [1] but this conversion is not time
critical, and the virtuals haven't stabilized yet, plus we wanted to fix
some (most) of the reverse deps on our own first before bothering with
the bugs, as it's usually more time consuming to file bugs than just fix them

In case you receive such an bug at later date, and you don't want to be
bothered about the change, just say so on the bug and the bug will be fixed for you.
But it's really straighforward, if your package uses one of the libs,
depend on the matching virtual, with the := in the end, otherwise it's virtual/udev
you want, without any := since it's not for libraries.

[1] http://bugs.gentoo.org/506034

Thanks,
Samuli



                 reply	other threads:[~2014-03-30 19:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5338694B.2030004@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@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