[oe] [oe-commits] org.oe.dev rootfs_ipk: as per OE policy: remove feed management tools
rod at whitby.id.au
Fri Mar 2 01:39:56 CET 2007
">" = RP, ">>" = Koen ...
> Mickey has a point here. There are a number of people upset by the
> recent deploy directory changes. I would like a calm rational discussion
> to take place before any further commits are made on this subject.
The voices of reason. Thank you.
> Personally, I'm currently undecided. I'd like to hear more from both
> sides. If there is a convincing reason for breaking deploy as a feed
> behaviour, I'm listening. If we can use deploy as a feed and just need
> to fix some broken tools, we should consider allowing that (even if its
> a case of user beware and not officially supported).
Unslung and SlugOS has been using an rsync of the tmp/deploy/ipk
directory (with no changes) for over two years, without a single
complaint from either developers or users.
>> All feed management was removed a long time ago from OE because
>> a) it's out of scope
I want it to be in scope. Who makes the decision as to what's in scope
and what's out of scope. If I want to bring something that was
previously out of scope (and we've seen no documentation that OE feeds
falls in this category, so I don't concede that at all), and it does not
affect any existing use of OE, then who makes the final decision on
whether it can be brought in scope or not? I truly hope it's not just
the will of a single developer, or a single distro ...
>> b) can't be done right in an automated fashion
> Can you explain b) a bit more?
Seconded. As stated above, Unslung and SlugOS have been doing this for
two years in an automated way with nothing more than "rsync" and what's
already in OE. No complaints from developers or users. No upgrade
problems. No bugs reported. That doesn't mean it works for any other
distros, but we haven't been given the technical information of how it
breaks for anyone yet ...
> I will add that feed generation is something that most OE users have to
> deal with at some point. It would be nice to have a wiki page or
> something showing some best practise in managing them. I know I'll have
> to face this with poky at some point and others are in a similar
> position. I don't think feed management should dictate how OE's
> directory structure works but I'm also not sure saying feed management
> is something external is a good idea either since we're all going to
> have to deal with it at some point.
If OE wants to ensure that developers and users handle feeds correctly,
then the support should (IMHO) be added to OE, so that any bugs in that
handling are fixed in a central place, rather than each distro or
maintainer or developer handling feed generation in multiple
incompatible ways ...
More information about the Openembedded-devel