| 1 |
Kumba wrote: |
| 2 |
> Essentially, to re-kickstart arm, several people need to work on a |
| 3 |
> single platform, and I know ARM is one of those really weird archs out |
| 4 |
> there with 200+ subdivisions. So say, take the Zaurus as a starting |
| 5 |
> point. Everyone with a Zaurus can work out in a place (say these MLs |
| 6 |
> for example, or the forums) and determine which packages work or don't |
| 7 |
> work, maintain a local portage tree, and feed major patches back to us |
| 8 |
> (like patches for glibc, gcc, and other *base-system* packages). Once a |
| 9 |
> minimal gentoo system on ARM can be built for a portage tree, I would |
| 10 |
> imagine that would go a long way to getting arm support readded to the |
| 11 |
> tree. As I stated in that forum thread, a majority of arm keywords were |
| 12 |
|
| 13 |
I see. If there were a handful of people willing to do this, how would |
| 14 |
they start about? As the current publinc portage tree does not contain |
| 15 |
the arm keyword for any package, would they have a separate, |
| 16 |
arm-development portage tree? They would make sure that certain packages |
| 17 |
compile, and insert details into the arm-development tree? Then somehow |
| 18 |
the changes would be merged into the main tree? |
| 19 |
|
| 20 |
|
| 21 |
Akos |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-embedded@g.o mailing list |
Archives