Re: IPFire 3.x packfire

Re: IPFire 3.x packfire

[Michael Tremer]

[-- 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
> >
> 

Aw: Re: IPFire 3.x packfire

[Bernhard Bitsch]

[-- 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
>

Re: Aw: Re: IPFire 3.x packfire

[Michael Tremer]

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

Development documentation is done in English, only.

Of course some people write better docs in their native language, but
not all are able to read this. If we would start documenting everything
in various languages, all of them would be incomplete and may have
different content.

As we have a lot of developers who all have different native languages,
English is the common denominator and I don't see the point in
translating everything to for example German, because that is also a
language some developers speak. It is not worth to do the work.

-Michael

On Sat, 2013-03-09 at 19:54 +0100, Bernhard Bitsch wrote:
> 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
> >