linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-sparse@vger.kernel.org, Josh Triplett <josh@freedesktop.org>
Subject: Re: sparse as a compiler front-end
Date: Sat, 11 Nov 2006 22:22:41 -0500	[thread overview]
Message-ID: <45569381.9000109@garzik.org> (raw)
In-Reply-To: <20061112030453.GA20415@humbolt.us.dell.com>

Matt Domsch wrote:
> On Sat, Nov 11, 2006 at 08:45:41PM -0500, Jeff Garzik wrote:
>> Matt Domsch wrote:
>>> On Sat, Nov 11, 2006 at 04:54:08PM -0500, Jeff Garzik wrote:
>>>> I see that sparse made it into Fedora Extras, so that 'yum install' 
>>>> automatically pulls it down for me.  Yay!  Thanks, Matt.
>>>>
>>>> Can libsparse.a and necessary includes be packaged as well?
>>> .a or .so?  The .so just got dropped from the standard sparse 'make
>> Doesn't matter to me...  Something is better than nothing.  With 
>> sparse's license, .a is no big deal.
> 
> Fedora Extras strongly discourages shipping and using .a if only to
> ensure that any security issue uncovered can be addressed without
> always rebuilding all downstream dependent apps.  Not too likely a
> problem with a tool like sparse, but always a concern.
> 
> The .so would need to start being versioned, and care paid to bump the
> version as the ABIs change.

Or alteratively we could recognize that sparse is a bit of an unusual 
lib.  With the library likely to be changing rapidly, caring about ABIs 
at this early stage probably isn't in anybody's best interests.

	Jeff

  reply	other threads:[~2006-11-12  3:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 21:54 sparse as a compiler front-end Jeff Garzik
2006-11-11 23:50 ` Matt Domsch
2006-11-12  1:45   ` Jeff Garzik
2006-11-12  3:04     ` Matt Domsch
2006-11-12  3:22       ` Jeff Garzik [this message]
2006-11-12  1:32 ` Josh Triplett
2006-12-05 16:53   ` Josh Triplett
2006-12-08 19:34     ` Matt Domsch
2006-12-09  9:43       ` Josh Triplett
2006-12-09 10:15         ` Jeff Garzik
2007-02-28  1:36           ` Josh Triplett
2006-12-09 10:17       ` Jeff Garzik
2006-12-09 16:17         ` Matt Domsch

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=45569381.9000109@garzik.org \
    --to=jeff@garzik.org \
    --cc=Matt_Domsch@dell.com \
    --cc=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).