On Mon, Sep 03, 2012 at 02:08:58PM +0000, Mark Bateman wrote: > Patrick Lauer <patrick <at> gentoo.org> writes: > > > > > On 06/23/12 21:21, Ciaran McCreesh wrote: > > > There's been a move towards using slots for "clever" things that don't > > > fit the traditional way of how slots worked. Examples include the new > > > gtk2 / gtk3 handling and Ruby gems virtuals. > > > > > > Aside from being abusive, > > No, it solves a real problem. > > > this screws things up for Paludis users. > > -EDONTCARE, use a supported package manager > > > > So if the packagemanager is struggling to resolve whether a package belongs > in a > slot or not, would this be a case for encoding such metadata in the ebuild > filename. > > foo-slot2-3.2.1.ebuild > > This way the PM would be able to determine exactly what it has todo before it > starts to parse the ebuild
No; the problem isn't getting the slot out of the metadata (moving it to the file name doesn't really do anything beyond make it slightly faster at the cost of being backwards incompatible for any existent PM that sees it); the problem is in the PMs resolver, and how it chooses to search the space. Basically, paludis does x, the rest do y; funky-slots was intended to make 'x' behave better at the cost of ebuild devs having to go mark shit up (leading to the retort 'do y instead'). ~harring
