[Trac #99] No mappings between build image and GIT commit ID.

[Zarro Boogs per Child]

#99: No mappings between build image and GIT commit ID.
-------------------------+--------------------------------------------------
 Reporter:  cjb          |        Owner:  blizzard
     Type:  enhancement  |       Status:  new     
 Priority:  normal       |    Milestone:  beta    
Component:  distro       |   Resolution:          
 Keywords:  build git    |  
-------------------------+--------------------------------------------------
Old description:

> It doesn't seem to be possible to checkout the version of sugar that went
> into build image 79 (for example).  Each build image (or sugar RPM)
> should be tagged with the GIT commit id for the repository it was built
> from.
>
> This doesn't solely apply to sugar, since we've had the same issue with
> buildrom; we should try to find a single solution for mapping build image
> numbers to GIT trees, and use it for all of the software we put on a
> build image that's coming from a GIT tree.

New description:

 The standard way to do this with git is to generate a rev id with `git-
 name-rev HEAD` during the build.

 This will yield <lasttagname>.<shortcommitid> , for example a patched on
 top of 1.4.2 of git itself gets "1.4.2.gdfe7"

Comment (by martinlanghoff):

 Replying to [ticket:99 cjb]:
 > It doesn't seem to be possible to checkout the version of sugar that
 went into build image 79 (for example).  Each build image (or sugar RPM)
 should be tagged with the GIT commit id for the repository it was built
 from.
 >
 > This doesn't solely apply to sugar, since we've had the same issue with
 buildrom; we should try to find a single solution for mapping build image
 numbers to GIT trees, and use it for all of the software we put on a build
 image that's coming from a GIT tree.

-- 
Ticket URL: <http://dev.laptop.org/ticket/99#comment:2>
One Laptop Per Child <http://laptop.org/>