public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [pre-GLEP] Gentoo binary package container format
Date: Sat, 17 Nov 2018 22:53:55 +0100	[thread overview]
Message-ID: <1542491635.828.1.camel@gentoo.org> (raw)
In-Reply-To: <raT+THU1uX74oR5H+xu5hc@se9O+1IlekjH/WN+pMIAw>

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

On Sat, 2018-11-17 at 14:05 +0000, Roy Bamford wrote:
> On 2018.11.17 11:21, Michał Górny wrote:
> > Hi,
> > 
> > Here's a pre-GLEP draft based on the earlier discussion on gentoo-
> > portage-dev mailing list.  The specification uses GLEP form as it
> > provides for cleanly specifying the motivation and rationale.
> > 
> > [snip glep proposal]
> > -- 
> > Best regards,
> > Michał Górny
> > 
> 
> Team,
>  
> One of the attractions of the existing format is that 
> tar xf /path/to/tarball -C /mnt/gentoo 
> works to fix things like glibc being removed and other
> missing essential portage components.
> 
> In effect, each binary package can be treated as a
> single package stage3 when a user needs a get out of jail
> free card.
> 
> Does this proposal allow for installing the payload without 
> the use of the Gentoo package manager from some random 
> distro being used as a rescue media?

Yes, and it can also be done via one-liner, though it's going to be more
complex than before, e.g.:

tar -xOf mypackage-1.gpkg.tar mypackage-1/image.tar.lz |
  tar --lzip -x -C /mnt/gentoo --strip-components 1

Though I wouldn't recommend using it but instead unpacking it normally
and inspecting the contents first.

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  parent reply	other threads:[~2018-11-17 21:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17 11:21 [gentoo-dev] [pre-GLEP] Gentoo binary package container format Michał Górny
2018-11-17 14:05 ` Roy Bamford
2018-11-17 14:17   ` Rich Freeman
2018-11-17 21:53   ` Michał Górny [this message]
2018-11-18  9:16 ` Fabian Groffen
2018-11-18  9:38   ` Michał Górny
2018-11-18 11:00     ` Fabian Groffen
2018-11-19 20:46       ` Kent Fredric
2018-11-21  9:33       ` Michał Górny
2018-11-21 10:45         ` Fabian Groffen
2018-11-21 11:20           ` Michał Górny
2018-11-26 21:13           ` Andrey Utkin
2018-11-27  8:32             ` Fabian Groffen
2018-11-18 11:04     ` Roy Bamford
2018-11-19 18:35 ` [gentoo-dev] [pre-GLEP r1] " Michał Górny
2018-11-19 19:21   ` Roy Bamford
2018-11-19 19:33     ` Rich Freeman
2018-11-19 19:40       ` Zac Medico
2018-11-19 19:51         ` Rich Freeman
2018-11-19 20:48       ` Roy Bamford
2018-11-20 20:34     ` Michał Górny
2018-11-20 20:33 ` [gentoo-dev] [pre-GLEP r2] " Michał Górny
2018-11-21 13:10   ` Fabian Groffen
2018-11-21 14:21     ` Michał Górny
2018-11-26 18:58 ` [gentoo-dev] [pre-GLEP r3] " Michał Górny
2018-11-26 19:17   ` Ulrich Mueller
2018-11-26 19:51     ` Michał Górny
2018-11-26 21:43   ` Roy Bamford
2018-11-30 17:06     ` Michał Górny
2018-11-30 21:23       ` Roy Bamford
2018-11-30 17:09 ` [gentoo-dev] [pre-GLEP r4] " Michał Górny
2018-12-01 10:25   ` Ulrich Mueller

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=1542491635.828.1.camel@gentoo.org \
    --to=mgorny@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