public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Resolving HAL vs. pciutils/usbutils
Date: Wed, 31 Oct 2007 11:40:02 -0400	[thread overview]
Message-ID: <4728A1D2.4020801@gentoo.org> (raw)
In-Reply-To: <47285D05.6090300@gentoo.org>

Daniel Drake wrote:
> Robin H. Johnson wrote:
>> Heya,
>>
>> So now this is not a flamewar.
>>
>> Jakub was originally going to complain at me for the upstream usbutils
>> adding support for gzipped usb.ids files, but a group of us (myself,
>> dsd, jakub, leio, steev) had a discussion about it, and came up with a
>> solution that both ends the breakage for direct users (HAL and others),
>> and provides forward momentum.
>>
>> So firstly, what's the real problem? The original complaint came up
>> because HAL expected the uncompressed file to exist as pci.ids, and
>> wasn't ready to look at pci.ids.gz. While this caused breakage, it was
>> only a warning sign that there was a deeper problem.
>
> I don't feel strongly enough to make an objection to your commit, but
> I think pciutils is doing the right thing, and despite me and Mike
> putting a hours into getting a decent HAL patch together the response
> I got was that as upstream they are simply "not interested" (no
> technical or logical objections provided), so I don't feel you should
> be putting workarounds in pciutils just to make HAL happy.
>
>
>
> Daniel
Daniel,

That's a LOAD of garbage and you know it. You're just straight away
making up stuff, essentially lying. You know damn well what the reasons
were since they were explained to you on numerous occasions.

When HAL evaluated the usage of  libpci the following issues were
identified:
 1) increased memory usage, to the point that HAL was not usable on the
OLPC project
 2) ABI breakage between patch revisions (i.e. x.y.z and x.y.z+1 were
not ABI compatible)
 3) no shared library
 4) the library calls exit() when it encounters an error in parsing it's
own pci.ids file which would kill the whole app using it.

There might have been more. I don't remember. Refer to ML discussions
and refer to IRC logs with me.

Now Mike (vapier) rectified #4 several pciutils releases ago by
providing a callback function that we could define which would override
the default exit() behavior. I still think it's sub-par to have an
utility library call exit() by default but whatever.

You were told by me and the HAL ML that once #2 and #3 are rectified and
if you could provide some basic memory usage information along with your
patch (i.e. show #1 isn't true anymore) that we would happily accept
your patch.

Now #2 and #3 are still not true in the latest release. There is no
guarantee by the pciutils maintainers that they will maintain ABI
compatibility while keeping the same .so version number. And there is
still no shared library built.

You addressed #1 on the mailing list with a simple statement, which I
will paraphrase. "It doesn't use more memory on my machine". To which
Danny K asked if you could provide some basic data behind that and you
never did.

As a result, 3 out of 4 concerns with your patch and pciutils were never
addressed and the issue was dropped on the HAL ML pending more feedback.
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2007-10-31 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31  1:56 [gentoo-dev] Resolving HAL vs. pciutils/usbutils Robin H. Johnson
2007-10-31 10:46 ` Daniel Drake
2007-10-31 11:04   ` [gentoo-dev] " Guilherme Amadio
2007-10-31 11:31     ` Jan Kundrát
2007-10-31 13:30   ` Ryan Hill
2007-10-31 15:09   ` [gentoo-dev] " Wulf C. Krueger
2007-10-31 14:56     ` Daniel Drake
2007-10-31 15:40   ` Doug Goldstein [this message]
2007-10-31 16:12     ` Roy Marples
2007-10-31 17:07       ` Rémi Cardona
2007-10-31 16:26     ` Daniel Drake
2007-10-31 16:41       ` Jan Kundrát

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=4728A1D2.4020801@gentoo.org \
    --to=cardoe@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