[oe] [RFC] move to opkg
skoroneos at digital-opsis.com
Mon Mar 24 08:55:49 CET 2008
I though a lot whether I should send this email or not and at the end come
up to the conclusion that its better to speak up although I run the risk of
having crowds with pitchforks coming after me :)
Recently I have been working on a part of a project that does not include OE
related development but tried to keep up with what is going on with OE
although not doing any active development, but that allowed me to have a
different perspective on things.
The problem I see is that .dev is turning into .experimental where all kind
of "infrastracture" changes get done with little or no afterthough
I do understand that .dev is just that, a development branch, and so
breakage is expected to happen, but I think recently we are having more days
with .dev in breakage than in a "working" state.
The main reason is that people simply don't use the SCM we have for the
reason we have it.
SCM's exists so,among other things, branches can be made, where experimental
code and "disruptive" changes can exists,without interfearing with the
Then one day these changes can either get merged to the main branch or
cherry pick what ever we want, after things get tested on the branch and
major issues are solved.
I know that the obvious answer to this, is "mtn sucks, we need <put your
favorite scm here>" but I strongly believe it's a matter of workflow and not
(for the record we use svn internally and mtn was an additional "pain" we
had to go over to use OE)
I've been with OE for the something like 3 years now and I have never seen
any developer create a branch to test big changes (with the exception of the
avr32 work I did with Koen, which by the way had almost 0 infrastracture
changes ) and things simply get "imported" into .dev after a (usually sort)
The other major issue I see more and more and I am sure we will face more in
the future, is that a lot of these infrastracture changes are coming from
companies that are using OE and are trying to "sync" OE with their
developments than the other way around.
I am not saying this is a bad thing, but I am just wondering what would
happen if for example one of choices they made for their OE based distro was
"not compatible" with the rest distro's or what would happen if the 2 major
commercial entities that use OE now decided to take a totally different
approach on a matter.
Change is a good thing (and that goes for opkg also) but as OE grows larger
we will face these issues more and more, so we better come up with a
solution before things get out of control.
And for closing this, let me clarify that I REALLY don't reffer to any
developer(s) in particular or even the recent opkg issue but it's my view of
what is going on.
Stelios S. Koroneos
Digital OPSiS - Embedded Intelligence
More information about the Openembedded-devel