public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libpcre.so.3 - Compatibility with Debian
Date: Sat, 13 Aug 2016 03:39:41 +1200	[thread overview]
Message-ID: <20160813033941.5d017bbe@katipo2.lan> (raw)
In-Reply-To: <eb1bd7c8-cda3-bf68-7ba4-2f69d9fafaa2@verizon.net>

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

On Fri, 12 Aug 2016 09:12:22 -0500
james <garftd@verizon.net> wrote:

> (also, I'm not hung up on 'Jentoo' as a name; perhaps 'Gintoo'?
> 
> (peace && hth),
> James

Way outside the scope needed here. However we pull off Zhenchoo, its
going to be built on top of portage and our package management with
extra bling.

That's what is necessary to empower people with "ready built" machines
to customize it in the direction of a "natural gentoo install"

All this converstation details is:

- Is a given technique good
- Can it be installed in tree without breaking things
- How do we do that
- Is there a place we can do it where the problem is isolated to a
  narrow spectrum of users to limit potential fallout
- Is this a "Put warning bells on it and let users blow off their own
  feet and then don't do it by default"[1] thing.
- Can this be a "Just package.mask the problem on hardened" thing.

All of those can be combined in some way to get and end result by
whoever ships the stage 4 the way they want to do it. They can use an
overlay if they want.

Nothing is stopping them :)

Other than themselves of course.

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

  reply	other threads:[~2016-08-12 15:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 23:10 [gentoo-dev] libpcre.so.3 - Compatibility with Debian James Le Cuirot
2016-08-11  5:53 ` Kent Fredric
2016-08-11 15:41   ` Mike Gilbert
2016-08-11 18:57   ` Patrick McLean
2016-08-18  5:45   ` Daniel Campbell
2016-08-11  9:43 ` Ulrich Mueller
2016-08-11 10:11   ` James Le Cuirot
2016-08-11 10:56     ` Ulrich Mueller
2016-08-11 11:20       ` James Le Cuirot
2016-08-11 11:49         ` Kristian Fiskerstrand
2016-08-11 12:04         ` Ulrich Mueller
2016-08-11 12:13           ` Rich Freeman
2016-08-11 14:57       ` Mart Raudsepp
2016-08-11 15:03         ` Ciaran McCreesh
2016-08-11 15:05         ` Ian Stakenvicius
2016-08-11 15:15           ` Mart Raudsepp
2016-08-11 19:56           ` James Le Cuirot
2016-08-11 20:07             ` Ian Stakenvicius
2016-08-11 21:34               ` Kent Fredric
2016-08-11 22:00                 ` Mike Gilbert
2016-08-12  1:19                   ` Mart Raudsepp
2016-08-18  6:06                     ` Daniel Campbell
2016-08-11 20:50             ` Michał Górny
2016-08-11 21:30               ` James Le Cuirot
2016-08-11 21:55               ` Mike Gilbert
2016-08-12  0:27               ` Patrick McLean
2016-08-12  0:32                 ` Kent Fredric
2016-08-12 14:12                   ` james
2016-08-12 15:39                     ` Kent Fredric [this message]
2016-08-12 17:40                       ` james
2016-08-12 17:48                         ` M. J. Everitt
2016-08-12 22:36                           ` Rich Freeman
2016-08-12 17:55                         ` Kent Fredric
2016-08-11 16:23 ` james
2016-08-11 16:32   ` Mart Raudsepp
2026-08-13 18:27     ` james
2016-08-11 18:02       ` Matt Turner
2016-08-11 18:27         ` Deven Lahoti

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=20160813033941.5d017bbe@katipo2.lan \
    --to=kentnl@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