| 1 |
* James <wireless@×××××××××××.com> wrote: |
| 2 |
|
| 3 |
Hi, |
| 4 |
|
| 5 |
> 4. Formalize a process where others (non devs) can build, store and |
| 6 |
> maintain ebuilds that are not blessed by the devs, so individuals |
| 7 |
> can easily share their work with the larger Gentoo community. |
| 8 |
|
| 9 |
Isn't this what several overlay projects (eg. Sunrise) are meant for ? |
| 10 |
IMHO, Sunrise suffers from it's size - lot's of smaller overlays |
| 11 |
could be the way to go. Maybe differenciate between bleeding-edge |
| 12 |
and production overlays ? |
| 13 |
|
| 14 |
AFAIK, the current overlay technique could be improved to make |
| 15 |
using *dozens* of overlays much easier. Some points I'm missing: |
| 16 |
per-overlay masking direct overlay selection when emerging. |
| 17 |
|
| 18 |
I'm using several overlays and I'd like to have exact control |
| 19 |
where specific ebuilds come from on updates. For example I have |
| 20 |
to change a few ebuilds from the main tree and take care that |
| 21 |
nothing get mixed up - updates from the main tree should not |
| 22 |
override older versions from my overlay, but I need to be |
| 23 |
informed about them. |
| 24 |
|
| 25 |
> If one choses such and ebuild there on their own. The gentoo devs |
| 26 |
> should develop a semantic where folks not officially part of the |
| 27 |
> devs can maintain a package or two, rather than making ebuilds for |
| 28 |
> obsolescence, unilaterally. |
| 29 |
|
| 30 |
Maybe a combination of overlays and proxy maintenance ? |
| 31 |
|
| 32 |
> 6. Provide resources to the gentoo-embedded group to assist them |
| 33 |
> in their efforts to assimilate embedded-gentoo into gentoo |
| 34 |
> so that lots of ordinary users can build and experiment with |
| 35 |
> embedded gentoo. |
| 36 |
|
| 37 |
Actually, as an embedded guy, I don't think that Gentoo (with it's |
| 38 |
current models) is really suitable for embedded systems (-> small |
| 39 |
devices, exotic platforms, ...). The concepts are fundamental |
| 40 |
opposite. For example, if you're not always crosscompiling within |
| 41 |
sysroot, you're seriously wrong for embedded systems ;-P |
| 42 |
|
| 43 |
I really doubt that it's really worth trying to make (current) |
| 44 |
Gentoo suitable for embedded systems, as major concepts are |
| 45 |
opposite and it would cause us big headache. |
| 46 |
|
| 47 |
BUT: I really think that an major distro like Gentoo should |
| 48 |
cooperate with embedded folks in an meta project like OSS-QM. |
| 49 |
For example, most of the collected patches could be a bit more |
| 50 |
generalized and then go to OSS-QM, while Gentoo could get it's |
| 51 |
directly from there. |
| 52 |
|
| 53 |
|
| 54 |
cu |
| 55 |
-- |
| 56 |
--------------------------------------------------------------------- |
| 57 |
Enrico Weigelt == metux IT service - http://www.metux.de/ |
| 58 |
--------------------------------------------------------------------- |
| 59 |
Please visit the OpenSource QM Taskforce: |
| 60 |
http://wiki.metux.de/public/OpenSource_QM_Taskforce |
| 61 |
Patches / Fixes for a lot dozens of packages in dozens of versions: |
| 62 |
http://patches.metux.de/ |
| 63 |
--------------------------------------------------------------------- |
| 64 |
-- |
| 65 |
gentoo-user@l.g.o mailing list |
Archives