On Sun, 17 Jun 2012 14:09:14 +0200 Thomas Sachau <to...@gentoo.org> wrote:
> Michał Górny schrieb: > > Hello, > > > > I have prepared a first draft of 'dynamic SLOT' specification. This > > is my proposal in attempt to solve the problem of building packages > > for multiple Python and Ruby versions. It could also be reused for > > multilib. > > > > The spec tries to explain the broad idea, and all problems relevant > > to it. It also lists a few problems which are still unsolved and I > > think they will cause the spec to change after hearing your ideas. > > > > To be honest, I tried to keep it as simple as possible. Please don't > > say it doesn't solve all the world problems because it simply won't. > > > > I'm attaching a reStructuredText version of the spec. You can view > > it rendered as a gist[1]. But please keep the replies on the list, > > rather than forking the gist. > > > > [1]:https://gist.github.com/2943774 > > > > Since you have not responded to my lines in IRC, i will repeat them > here: > > First: How does the user see, which slots are possible and which ones > are currently active and which are currently not selected? Implementation is left to be package-manager specific. I guess colorful output (similar to USE flags) would be enough. > Beside that, it seems to solve things pretty similar to the proposed > way in multilib-portage for cross-compiling (which could also be > adapted for multi-slot languages) with different wording and with > additional work for ebuild maintainers. And since my proposal already > uses USE flags, things would not change visually for users of e.g. > ruby or php. I'm sad you aren't even trying to listen. Your attempt implies that every single change in targets requires rebuilding all of them. If I weren't using 32-bit libs, and now I want to compile 32-bit wine, I have to recompile most of my libraries for both ABIs. That is a no go for me. And adjusting that for other multi-slot languages is pointless. Because they do the same already. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
