[oe-issues] [Bug 2919] Create a distro for gumstix

bugzilla-daemon at tinman.treke.net bugzilla-daemon at tinman.treke.net
Wed Sep 5 18:24:37 UTC 2007


http://bugs.openembedded.org/show_bug.cgi?id=2919





--- Comment #17 from Koen Kooi <koen at dominion.kabel.utwente.nl>  2007-09-05 11:24:36 ---
(In reply to comment #15)
> (In reply to comment #14)
> 
> > I recognize there is a need for a derivative distro, in the openmoko cases all
> > parties agreed on it. In the gumstix case I'm having this discussion to see if
> > it's really needed or (don't take this the wrong way) the usual thing of
> > believing to be 'special'. A big number of bogus arguments are being used,
> > which I want to counter :)
> 
> I guess the specialness in the gumstix case is several thousand users who might
> start using OE if we switch to it as the primary build platform for gumstix. 

Homer: There are 3 ways to do it: the right way, the wrong way and the Homer
Simpson way.
Bart: Isn't the homer way the wrong way?
Homer: Yes, but faster.

> Many of those users have AOL-level sophistication.  Many will probably switch
> from building themselves to using pre-built .ipkgs, but that will make it even
> more important that when they find an .ipkg somewhere,

"somewhere" being the operative word...

> it'll actually work on their gumstix, including correct libc, etc.

Having a derived distro doesn't help against that. AOL type uses will download
and try to install anything that ends in .ipk, even if you make it clear that
only stuff in the gumstix package repos will work.

To solve that you have to extend the ipkg format and patch ipkg itself to only
allow "gumstix-leet-uclibc" ipkgs ( or .debs or .rpms, etc).

As I hinted at earlier, I'm not against having a gumstix distro as an
angstrom-derivative, but the majority of your arguments aren't making sense in
an OE context (don't feel bad, OE is weird in that way).

The arguments that do make sense (control, branding) are key ones.

And why do people keep insisting on newer udevs without giving concrete answers
on why? The previous person that insisted on it couldn't get further than
pasting the changelog and saying something that summarizes as "OMG newer!!!".
Please file bugs on what is broken in 092 and specify how a newer version fixes
that bugs. If it fixes big bugs we can make 115 and OE wide default or and
angstrom wide default.


-- 
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.




More information about the Openembedded-issues mailing list