| 1 |
Brian Harring schrieb: |
| 2 |
> |
| 3 |
> You need a glep here frankly; per the norm, if you want things to move |
| 4 |
> faster, then put in time- aka, generate a patch against PMS, write a |
| 5 |
> patch for portage, etc, you get the idea. The bit re: a PMS patch is |
| 6 |
> mostly that in looking at your proposal... well, I personally don't |
| 7 |
> want to write that patch (nor do I suspect ulm/ciaran do either). |
| 8 |
|
| 9 |
As written earlier, a patch for portage exists already (just the diff |
| 10 |
between multilib and master branch of portage). |
| 11 |
Now, in addition, a GLEP draft for cross-compile support in |
| 12 |
multilib-portage. |
| 13 |
|
| 14 |
> |
| 15 |
> One thing to note; this has been posted for all of 2-3 days; that's |
| 16 |
> not exactly much time for 1) people to comment, 2) people to frankly |
| 17 |
> comprehend the quite dense description you wrote. |
| 18 |
|
| 19 |
This may be true, but as you may have seen afterwards, beside the |
| 20 |
responses to my mail about planned council asking, there have not been |
| 21 |
any further responses, so the relatively short time since my mail doesnt |
| 22 |
seem like the reason for missing responses. |
| 23 |
|
| 24 |
> |
| 25 |
> Please write a glep covering details of the implementation, |
| 26 |
> background, preferablly why this route over others. Bluntly... clue |
| 27 |
> everyone else in rather than hoping they'll just sign off on a fairly |
| 28 |
> opaque list of things. :) It'll be useful for dev education also- |
| 29 |
> which is a bit of a requirement for stuff of this sort considering |
| 30 |
> it's not going to be a magic deploy/shit works everywhere situation I |
| 31 |
> suspect. |
| 32 |
|
| 33 |
See attached GLEP draft. |
| 34 |
|
| 35 |
> |
| 36 |
> Would also be useful getting commentary from crossdev folk considering |
| 37 |
> your solution is intended to be (best I can tell) full cross |
| 38 |
> compilation support, and they've been leading that front for many, |
| 39 |
> many years. |
| 40 |
|
| 41 |
There is an important difference between my cross-compile support for |
| 42 |
multilib profiles and crossdev: My suggestion works with the default |
| 43 |
toolchain, which itself is able to cross-compile for other targets (like |
| 44 |
the amd64/multilib gcc is able to create 32bit libs), while crossdev is |
| 45 |
using a different toolchain for the targets. |
| 46 |
|
| 47 |
Of course, if someone from crossdev maintainers wants to comment, he is |
| 48 |
free to do so. |
| 49 |
|
| 50 |
|
| 51 |
-- |
| 52 |
|
| 53 |
Thomas Sachau |
| 54 |
Gentoo Linux Developer |
Archives