#6470 NORM Never A: olpc-update doesn't let users manage their software builds
Zarro Boogs per Child
bugtracker at laptop.org
Thu Feb 21 04:45:05 EST 2008
#6470: olpc-update doesn't let users manage their software builds
------------------------------+---------------------------------------------
Reporter: gnu | Owner: cscott
Type: defect | Status: new
Priority: normal | Milestone: Never Assigned
Component: upgrade utility | Version: Development build as of this date
Resolution: | Keywords:
Verified: 0 | Blocking:
Blockedby: |
------------------------------+---------------------------------------------
Comment(by gnu):
Here's an example of how others also don't understand olpc-update:
Date: Wed, 20 Feb 2008 16:15:36 -0500
From: Mikus Grinbergs <mikus at bga.com>
To: devel at laptop.org
Subject: where did cross-build customization come from ?
FYI -- don't intend to do anything about it -- just letting you know
I had a strange experience.
I keep both a Joyride build and an Update.1 build on my G1G1; I
switch between them with the 'O' button at boot. Today I used
'olpc-update' (from Joyride) to install the latest Update.1, then
used 'olpc-update' (from Update.1) to install the latest Joyride.
I normally apply various customizations in /etc and in /usr (e.g.,
to disable frame "auto-raise", and to preset some environmental
variables). The way I remember it, having booted this latest
Joyride build I manually edited-in my changes. But then when I
booted the latest Update.1 build, I found the /etc and /usr changes
already made.
It might be Alzheimer's that is making me forget applying my changes
twice. But I am left with the question: "how come my edits showed
up with both builds, when I remember making my edits only once ?"
mikus
--
Ticket URL: <http://dev.laptop.org/ticket/6470#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list