Re: [Ltib] BSP releases and repository tags

[Stuart Hughes]

Hi Andrea,

The release tag does get written into the ISO image, this is under
release_logs/RELEASE_INFO in recent releases.  In there you may see
something like this (comment below each line describing each entry):

Release date = Wed Aug 27 15:22:49 2008 UTC
        When it was made
Release user = seh
        Use id of who made it
Release host = m20
        Hostname on which the release was made
Release dir  = /home/seh/ltib_bsps/fc5
        The directory from where it was made
SCM wtag     = Tbranch-xxxx-sim_b1
        The branch you made it from     
SCM tag      = branch-xxxx-sim_b1
        The actual tag for this release
Release tag  = ltib-e500mc-20080827
        The ISO tag name (descriptive)
App version  = 8.1.2
        ltib script release version
CVS version  = $Revision: 1.393 $
        ltib script CVS version

Note that this also gets written into the root filesystem as
/etc/ltib-release.  When you first install an ISO without any changes,
this will be the same as on the ISO.  However, if you modify and rebuild
in anyway, this will get changed as it is no longer the _actual_ release.

Regards, Stuart

On 21/01/11 09:51, Andrea Galbusera wrote:
> Hello,
> I'm currently maintaining a series of ltib BSPs for an internal project.
> We track BSP configuration changes and fixes with our company CVS
> repository. For any new BSP release we use './ltib -m release'. This
> works fine for us and provide a self contained copy of everything needed
> for generating target images of any released BSP version. Branching and
> tagging strategies we adopted are the same as described in
> doc/LtibReleaseProcess. 
> 
> Here comes my question: is there any reference to the release tag we
> specify while running './ltib -m release' inside the rootfs image that
> comes with the generated ISO? I thought this could have been in the
> included /etc/ltib-release, but it does not seem so.
> 
> My final goal is to read the BSP version from a running target: the most
> desirable 'version string' would be the CVS tag corresponding to that
> specific BSP version.
> 
> Could anybody please elaborate on the /etc/ltib-release and RELEASE_INFO
> files logic and how they get managed when ISO releasing with './ltib -m
> release'?
> 
> Thanks in advance
> Regards,
> 
>