Things seem to be progressing nicely on this front. We have answers to the questions people had and they look satisfactory to me.
One thing that I think would be valuable is a document that explains the average dev how to make his/her ebuilds prefix compliant with links to more details when necessary. I understand that there's the trivial situations and the less trivial ones. In the latter case it would be nice to explain why the case isn't trivial and how to fix it. Using python as an example could be one way to do it. I'm thinking of something practical that could possibly be patched into devmanual. If such a document already exists then please just point us to it. On Fri, Nov 20, 2009 at 2:03 AM, Fabian Groffen <grob...@gentoo.org> wrote: >> I thought I asked Fabian to work on that at the end of the meeting. In >> case I didn't then consider this as me officially asking him if he can >> take care of it. Fabian is this OK with you? > > Yes, I agreed coming up with some patch. I admit I haven't yet even > looked into it. Great, thanks. If you can have it ready some time before the meeting so that all devs can get a chance to review it before the council members vote on it that will be even better. If you need help don't hesitate to contact me. I'll try and look for the right people to help you depending on what you need. > Technically, Portage trunk already contains the most important bits that > allow us to continue since yesterday. The rest is waiting for a formal > approval of the council, and then it will most probably be me and Zac > fighting to get the prefix branch merged into trunk. Good. > Next to that, it is part of the Prefix team's job to make sure that > whatever is installed, does not reference the host system when this is > not absolutely necessary. Could you give some examples of when it is absolutely necessary? Denis.
