[Fwd: Re: bitbake freeze]

[Fwd: Re: bitbake freeze]

[Øyvind Repvik]

Michael 'Mickey' Lauer wrote:
> Am Montag, den 04.09.2006, 00:28 -0700 schrieb Justin Patrin:
>> I just remembered the old "freeze" command that John Bowler wrote a
>> while ago and tried to use it. Unfortunately it doesn't seem to work
>> with the current OE.
> 
> [...]
> 
>> I realize the shell isn't really the right place for this and that
>> this might be nicer in a bb file somewhere but this is how I could get
>> it working.
> 
> The shell is _exactly_ the right place for it -- since the command line
> parsing
> went so fast, we need to come up with new use cases ;)
> 
>> Let me know what you think and any suggestions for making the code better.
> 
> I'm not familiar with the old freeze command (or I forgot it...), can
> you summarize
> what you want to achieve?
> 
The old freeze command looked at what had been built, and made a config
file with a BBFILES variable that specified each specific .bb-file used
(eg. samba_3.0.20.bb, glibc_2.3.3+cvs20050420.bb, etc.). The effect was
more or less "freezing" the the build, making a release easier.

Regards,
Øyvind Repvik

Re: [Fwd: Re: bitbake freeze]

[Justin Patrin]

On 9/4/06, Øyvind Repvik <nail@nslu2-linux.org> wrote:
>
> Michael 'Mickey' Lauer wrote:
> > Am Montag, den 04.09.2006, 00:28 -0700 schrieb Justin Patrin:
> >> I just remembered the old "freeze" command that John Bowler wrote a
> >> while ago and tried to use it. Unfortunately it doesn't seem to work
> >> with the current OE.
> >
> > [...]
> >
> >> I realize the shell isn't really the right place for this and that
> >> this might be nicer in a bb file somewhere but this is how I could get
> >> it working.
> >
> > The shell is _exactly_ the right place for it -- since the command line
> > parsing
> > went so fast, we need to come up with new use cases ;)
> >
> >> Let me know what you think and any suggestions for making the code better.
> >
> > I'm not familiar with the old freeze command (or I forgot it...), can
> > you summarize
> > what you want to achieve?
> >
> The old freeze command looked at what had been built, and made a config
> file with a BBFILES variable that specified each specific .bb-file used
> (eg. samba_3.0.20.bb, glibc_2.3.3+cvs20050420.bb, etc.). The effect was
> more or less "freezing" the the build, making a release easier.
>

That's one use-case. My current code doesn't do this yet (although it
should be simple to fix it)..

Ok, it's fixed and the patch is updated.

My use-case for this is to get a list of the packages which have been
built in order to just update the packages in my personal feed. This
way I can just "mtn up" and "bitbake -k world" to update to the
current versions of these packages (similar to "emerge -u world" in
portage).

Now the freeze command will output 2 files.
frozen-bbfiles.conf is a list of all of the specific bbfiles which
provide all of the build packages.
BBFILES := "\
/home/papercrane/oe/org.openembedded.oz354x/packages/alsa/alsa-settings_0.0.1.bb
\
/home/papercrane/oe/org.openembedded.oz354x/packages/alsa/alsa-utils_1.0.10.bb \
/home/papercrane/oe/org.openembedded.oz354x/packages/altboot/altboot_1.0.8.bb \
/home/papercrane/oe/org.openembedded.oz354x/packages/apmd/apmd_3.2.2.bb \
...

frozen-packages.conf is a list of all of the packages which provide
all of the built packages
BBFILES := "\
/home/papercrane/oe/org.openembedded.oz354x/packages/alsa/*.bb \
/home/papercrane/oe/org.openembedded.oz354x/packages/altboot/*.bb \
/home/papercrane/oe/org.openembedded.oz354x/packages/apmd/*.bb \
/home/papercrane/oe/org.openembedded.oz354x/packages/atd/*.bb \
/home/papercrane/oe/org.openembedded.oz354x/packages/autoconf/*.bb \

-- 
Justin Patrin

Re: [Fwd: Re: bitbake freeze]

[Justin Patrin]

On 9/4/06, Justin Patrin <papercrane@gmail.com> wrote:
> On 9/4/06, Øyvind Repvik <nail@nslu2-linux.org> wrote:
> >
> > Michael 'Mickey' Lauer wrote:
> > > Am Montag, den 04.09.2006, 00:28 -0700 schrieb Justin Patrin:
> > >> I just remembered the old "freeze" command that John Bowler wrote a
> > >> while ago and tried to use it. Unfortunately it doesn't seem to work
> > >> with the current OE.
> > >
> > > [...]
> > >
> > >> I realize the shell isn't really the right place for this and that
> > >> this might be nicer in a bb file somewhere but this is how I could get
> > >> it working.
> > >
> > > The shell is _exactly_ the right place for it -- since the command line
> > > parsing
> > > went so fast, we need to come up with new use cases ;)
> > >
> > >> Let me know what you think and any suggestions for making the code better.
> > >
> > > I'm not familiar with the old freeze command (or I forgot it...), can
> > > you summarize
> > > what you want to achieve?
> > >
> > The old freeze command looked at what had been built, and made a config
> > file with a BBFILES variable that specified each specific .bb-file used
> > (eg. samba_3.0.20.bb, glibc_2.3.3+cvs20050420.bb, etc.). The effect was
> > more or less "freezing" the the build, making a release easier.
> >
>
> That's one use-case. My current code doesn't do this yet (although it
> should be simple to fix it)..
>
> Ok, it's fixed and the patch is updated.
>
> My use-case for this is to get a list of the packages which have been
> built in order to just update the packages in my personal feed. This
> way I can just "mtn up" and "bitbake -k world" to update to the
> current versions of these packages (similar to "emerge -u world" in
> portage).
>
> Now the freeze command will output 2 files.
> frozen-bbfiles.conf is a list of all of the specific bbfiles which
> provide all of the build packages.
> BBFILES := "\
> /home/papercrane/oe/org.openembedded.oz354x/packages/alsa/alsa-settings_0.0.1.bb
> \
> /home/papercrane/oe/org.openembedded.oz354x/packages/alsa/alsa-utils_1.0.10.bb \
> /home/papercrane/oe/org.openembedded.oz354x/packages/altboot/altboot_1.0.8.bb \
> /home/papercrane/oe/org.openembedded.oz354x/packages/apmd/apmd_3.2.2.bb \
> ...
>
> frozen-packages.conf is a list of all of the packages which provide
> all of the built packages
> BBFILES := "\
> /home/papercrane/oe/org.openembedded.oz354x/packages/alsa/*.bb \
> /home/papercrane/oe/org.openembedded.oz354x/packages/altboot/*.bb \
> /home/papercrane/oe/org.openembedded.oz354x/packages/apmd/*.bb \
> /home/papercrane/oe/org.openembedded.oz354x/packages/atd/*.bb \
> /home/papercrane/oe/org.openembedded.oz354x/packages/autoconf/*.bb \
>

I keep forgetting to mention that this is against the 1.6 branch.

-- 
Justin Patrin