All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Jeff Layton <jlayton@redhat.com>, linux-sparse@vger.kernel.org
Subject: Re: [SPARSE] Questions for distros
Date: Sat, 4 Nov 2017 18:56:29 +0100	[thread overview]
Message-ID: <13e9688b-0643-0a87-a87b-6c72192669b6@kleine-koenig.org> (raw)
In-Reply-To: <1509817409.29302.14.camel@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]

Hi Luc,

On 11/04/2017 06:43 PM, Jeff Layton wrote:
> On Sat, 2017-11-04 at 18:25 +0100, Luc Van Oostenryck wrote:
>> Hi,
>>
>> I'm making some cleanup in my dev tree and there are a few things
>> I'm curious about concerning what distros are doing.
>>
>> I hope you don't mind to answer to those questions.
>>
>> 1) Do the distros use sparse's shared lib?
>>    I remember there was a mail about it months ago but 
>>    I can't find it anymore.
>>
> 
> The Fedora and EPEL packages do not. I'm not opposed to adding it, but I
> don't really need it and no one has asked for it.
> 
>> 2) Do the distros use sparse's install rule?
>>
> 
> Yes. rpmbuild basically does a make install in a chrooted dir, and then
> installs the files that end up in there.
> 
>> 3) Do the distros install sparse with its pkconfig?
> 
> No. Since we aren't packaging the shared lib, we don't bother.
> 

The answers for Debian are exactly the same. Ubuntu uses the Debian
packages as is.

https://packages.debian.org/sid/sparse (and
https://packages.debian.org/sid/sparse-test-inspect) have "list of
files" links for each architecture which might be quicker to answer
similar questions for you. (But I don't mind your questions.)

Best regards
Uwe


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-11-04 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 17:25 [SPARSE] Questions for distros Luc Van Oostenryck
2017-11-04 17:43 ` Jeff Layton
2017-11-04 17:56   ` Uwe Kleine-König [this message]
2017-11-04 20:13     ` Luc Van Oostenryck
2017-11-04 20:01   ` Luc Van Oostenryck

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=13e9688b-0643-0a87-a87b-6c72192669b6@kleine-koenig.org \
    --to=uwe@kleine-koenig.org \
    --cc=jlayton@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.