public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: IPFire 3.x packfire
Date: Sat, 09 Mar 2013 19:54:56 +0100	[thread overview]
Message-ID: <trinity-bd80d905-83f0-4c2c-8a99-3eb485a0bd1a-1362855296303@3capp-gmx-bs64> (raw)
In-Reply-To: <1362733223.9109.1.camel@rice-oxley.tremer.info>

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

Just a thought about this problem:
Wouldn't it be better to publish development docu in the native language of the publisher?
I know, to be general we should publish in English.
But most ( all? ) men are able express thoughts most exact in their native language ( there is a reason it is called "Muttersprache" in German ).

A translation native --> English could be made by a native english speaker with knowledge of the other language. Sure this translation should be approved be the author.


Bernhard

> Gesendet: Freitag, 08. März 2013 um 10:00 Uhr
> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> An: "Thomas Ebert" <th.ebert(a)gmx.de>
> Cc: development(a)lists.ipfire.org
> Betreff: Re: IPFire 3.x packfire
>
> 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
> > >
> >
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>

  reply	other threads:[~2013-03-09 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5139A3B7.5070503@gmx.de>
2013-03-08  9:00 ` Michael Tremer
2013-03-09 18:54   ` Bernhard Bitsch [this message]
2013-03-09 23:21     ` Aw: " Michael Tremer

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=trinity-bd80d905-83f0-4c2c-8a99-3eb485a0bd1a-1362855296303@3capp-gmx-bs64 \
    --to=bernhard.bitsch@gmx.de \
    --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