From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 3.x packfire
Date: Fri, 08 Mar 2013 10:00:23 +0100 [thread overview]
Message-ID: <1362733223.9109.1.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <5139A3B7.5070503@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2779 bytes --]
Okay, then we don't have an error in the code base.
I tried to clarify what happens in a couple of sentences on which I was
not quite successful:
http://wiki.ipfire.org/devel/pakfire/architecture#clean_build_environments
Maybe some else can improve that?
-Michael
On Fri, 2013-03-08 at 09:39 +0100, Thomas Ebert wrote:
> Tnanks for the explanation Michael.
>
> As i mentioned before, that pakfire3 doesn't re-download the packages.
> ... they are not deleted!
>
> I missunderstood the output.
>
> Regards Thomas
>
>
> Am 08.03.2013 00:00, schrieb Michael Tremer:
> > Yes, the build environment is cleaned up after every build. This is
> > intentional, so you start every build in a clean environment and don't
> > get caught up in any errors.
> >
> > However, the downloaded package files are never deleted.
> >
> > Are you sure you see a re-download or just the extraction?
> >
> > -Michael
> >
> > On Thu, 2013-03-07 at 18:38 +0100, Thomas Ebert wrote:
> >> Hello out there.
> >>
> >> I know most of you are very busy at the moment, but could anybody of you
> >> provide an answer of my question?
> >> ... Is it normal that the build environment is cleaned everytime if you
> >> exit from it and start the command "pakfire-builder shell"?
> >>
> >> Regards
> >> Thomas
> >>
> >> Am 01.03.2013 13:43, schrieb Thomas Ebert:
> >>> Sorry. I missunderstood the output. Packfire is using local packages
> >>> as you described. But what about the build chroot environment. Is it
> >>> normal that the build environment is cleaned everytime if you exit
> >>> from it and start the command "pakfire-builder shell".
> >>>
> >>> Here is the paste from my shell: http://pastebin.com/fKn3UECQ
> >>>
> >>> This is my configuration /etc/pakfire/builder.conf
> >>>
> >>> [logger]
> >>>
> >>> # Use a different log file for the builder stuff.
> >>> file = /var/log/pakfire-builder.log
> >>>
> >>> [builder]
> >>> # Select the distribution to build for.
> >>> distro = ipfire3
> >>>
> >>> # Use ccache in order to build rebuilds in less time.
> >>> use_ccache = true
> >>>
> >>> # Use icecream in order to speed up builds.
> >>> use_icecream = false
> >>>
> >>> # Create build environments in a tmpfs.
> >>> # This requires a lot of RAM.
> >>> # Only enable if you know what your are doing.
> >>> #use_tmpfs = false
> >>>
> >>> # Create loop devices in build environment.
> >>> #use_loop_devices = true
> >>>
> >>> Regards
> >> _______________________________________________
> >> Development mailing list
> >> Development(a)lists.ipfire.org
> >> http://lists.ipfire.org/mailman/listinfo/development
> >
> > _______________________________________________
> > Development mailing list
> > Development(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/development
> >
>
next parent reply other threads:[~2013-03-08 9:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5139A3B7.5070503@gmx.de>
2013-03-08 9:00 ` Michael Tremer [this message]
2013-03-09 18:54 ` Aw: " Bernhard Bitsch
2013-03-09 23:21 ` Michael Tremer
[not found] <512FDB9A.1060009@gmx.de>
2013-03-01 12:06 ` Michael Tremer
2013-03-01 12:43 ` Thomas Ebert
2013-03-07 17:38 ` Thomas Ebert
2013-03-07 23:00 ` Michael Tremer
2013-02-26 22:53 Thomas Ebert
2013-02-27 15:14 ` Michael Tremer
2013-02-27 15:22 ` Thomas Ebert
2013-02-27 15:32 ` Michael Tremer
2013-02-27 15:37 ` Thomas Ebert
2013-02-27 15:52 ` Michael Tremer
2013-02-27 16:04 ` Thomas Ebert
2013-02-27 16:05 ` Michael Tremer
2013-02-27 16:13 ` Thomas Ebert
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=1362733223.9109.1.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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