public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Jones <gentoo@jonesmz.com>
To: William Hubbs <williamh@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Do (old-ish) Portage QA checks comprise policy?
Date: Mon, 4 Nov 2019 14:05:19 -0600	[thread overview]
Message-ID: <CABfmKSLT3mJKvKiwzeHPdmfi8pdUzn3fQE8N3WZOKOmmrr6+BA@mail.gmail.com> (raw)
In-Reply-To: <20191104192643.GA8436@whubbs1.dev.av1.gaikai.org>

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

On Mon, Nov 4, 2019 at 1:26 PM William Hubbs <williamh@gentoo.org> wrote:

>  That way is not building static libraries at all. If we go that way as
>  a distro the support for forcing static libraries into /usr/lib* is not
>  needed because we would just not allow static libraries.
>

As an end user, I would be unhappy if static libraries were no longer
supported at all. I use them regularly for my development work.

[-- Attachment #2: Type: text/html, Size: 772 bytes --]

  reply	other threads:[~2019-11-04 20:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 15:01 [gentoo-dev] Do (old-ish) Portage QA checks comprise policy? Michał Górny
2019-11-04 15:53 ` Michael Orlitzky
2019-11-04 16:02   ` Michał Górny
2019-11-04 16:07     ` Michael Orlitzky
2019-11-04 19:26       ` William Hubbs
2019-11-04 20:05         ` Michael Jones [this message]
2019-11-04 21:51           ` William Hubbs
2019-11-04 19:40   ` William Hubbs
2019-11-04 23:17     ` Michael Orlitzky
2019-11-04 23:24       ` Michael 'veremitz' Everitt
2019-11-05 10:41         ` Kent Fredric
2019-11-05  0:17       ` William Hubbs
2019-11-05  0:47         ` Michael Orlitzky
2019-11-04 21:50   ` Kent Fredric
2019-11-04 22:02     ` William Hubbs
2019-11-05  2:26   ` Andreas K. Huettel

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=CABfmKSLT3mJKvKiwzeHPdmfi8pdUzn3fQE8N3WZOKOmmrr6+BA@mail.gmail.com \
    --to=gentoo@jonesmz.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=williamh@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