That will be great, i was looking for something like this. On Thu, Nov 25, 2010 at 9:11 AM, Jerry Vonau <[email protected]> wrote:
> On Wed, 2010-11-24 at 22:49 +0000, Daniel Drake wrote: > > On 24 November 2010 22:40, Kevin Gordon <[email protected]> wrote: > > > Is this recommendation against yum and rpm for all software, or just > the > > > oplc repo packages, the kernel and the firmware? I'm certainly happy > doing > > > just safe builds for the core. > > > > To avoid all corner cases it the recommendation really needs to be > "everything" > > In reality, you'll probably get away with it, especially because > > you're only really working with added packages in your deployment (not > > upgrading ones that are already installed). > > > > Some of the resultant problems will also not affect small deployments > > like yours. For example, one side effect is that olpc-update pristine > > (efficient) updates stop working as soon as you make any filesystem > > modifications like this. Another side effect is that your > > custom-installed packages will magically disappear after an > > olpc-update upgrade (which in a real deployment would happen without > > you even knowing). > > > > But in a small deployment like yours, touching each laptop for updates > > is probably more sensible than the knowledge and infrastructure > > investment needed for hands-off olpc-update, so you aren't affected. > > > > > However, as part of our 'refresh' stick when we wipe and install a new > > > signed build, we generally also include the necessary rpm's for cheese > and a > > > couple of other utilities that are locally installed from the USB stick > > > using a bash script; or, for the Vernier software dependencies, the > > > dependent rpm's are installed by means of a python script. However, > they > > > are rpm's and they are downloaded onto the stick (the first time) using > yum, > > > and they are then installed from the stick using --localinstall from > the > > > stick. > > > > You probably won't see any problem with this collection of changes. > > Nevertheless, at the SF summit I started showing Adam the "correct" > > way to do this: building a custom OS image with those customizations > > already included. We didn't have time to completely finish it, but he > > picked it up quickly and could probably finish it with a little effort > > (and perhaps a couple of mails to this list). > > Having os-builder required to have net access in ksmain.50.repos.py is > less than ideal for remote image creation. Once the cache is downloaded > could we not just run createrepo on the cache and point os-builder to > the local url instead of going out to the net all the time? something > like: > > if use_cache: > url = "file:///%s/imgcreate/%s" %(ooblib.cachedir, name) > else: > url = "http://mock.laptop.org/repos/%s"; % name > > Attached is a rough diff of what I have in mind. > > On a side note both 10.1.2 and 10.1.3 share the the same olpc repo via > os-builder > (http://xs-dev.laptop.org/~dsd/repos/<http://xs-dev.laptop.org/%7Edsd/repos/>), > that makes it harder to tell the break > between the two. Now it's impossible to re-spin os852 without hard-coding > the > rpm versions elsewhere in os-builder. Just a thought. > > > Jerry > > > > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.laptop.org/listinfo/devel > > -- Javid Alam Software Developer and Technical support Officer OLPC Ministry of Education Kabul Afghanistan contact: +93(0)798123451 alternative email: [email protected]
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
