From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] quickpkg on a complete system?
Date: Mon, 19 Mar 2012 00:09:01 +0200 [thread overview]
Message-ID: <20120319000901.7ea550ec@khamul.example.com> (raw)
In-Reply-To: <CAK2H+eeNC1yV88uMMUYa5inWOOVh1Pfj9ZHY2uP9adqJUNv01A@mail.gmail.com>
On Sun, 18 Mar 2012 14:18:22 -0700
Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
> I have a system in which I've never used the buildpkg feature so I
> have no packages. The machine is completely up to date - i.e. - emerge
> -DuN @world does nothing new.
>
> I know if I turn on buildpkg and do an emerge -e @world, assuming
> all the compiling completes without error, emerge will create packages
> for everything that's install. That however takes lots of time.
>
> I was reading about the quickpkg feature which supposedly creates
> packages from what's already installed, but I'm not sure how to
> actually run that for a complete system like this. If I put
> FEATURES="quickpkg" in make.conf and run emerge -e @world, will emerge
> simply make the packages for anything that's already installed, but
> not actually compile the packages themselves?
>
> Thanks,
> Mark
>
RTFM :-)
"man quickpkg" lists "quickpkg @system" in the examples section.
"quickpkg @world" works and does what you expect - tar and gzips the
entire package as it is on-disk. As to what is in the quickpkg, it's
the same list as you get from "equery files <pkg_name>.
Thereafter, enable FEATURES="quickpkg" and portage will keep everything
new up to date.
Also read up on eclean, which helps to remove old quickpkg cruft
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-03-18 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 21:18 [gentoo-user] quickpkg on a complete system? Mark Knecht
2012-03-18 22:00 ` [gentoo-user] " Mark Knecht
2012-03-18 22:09 ` Alan McKinnon [this message]
2012-03-18 23:10 ` [gentoo-user] " Mark Knecht
2012-03-18 23:40 ` Pandu Poluan
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=20120319000901.7ea550ec@khamul.example.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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