On Sun, May 24, 2009 at 10:34 PM, <[email protected]> wrote: > Adding "@overlay" atoms/deps postfix support could really make life > easier, especially because forcing specific atoms in *DEPEND hoping > that these will be always pulled in from the same overlay is not > something reliable, as you already know. > > Examples: > > app-foo/f...@overlay > app-foo/foo:2...@overlay > foo:2...@overlay > f...@overlay > > Comments are welcome, flames are not.
Won't this just lead to dependency hell? With horrible dependencies between different overlays? The current system of "overlays" being restrictive is (IMO) beneficial in the long-term because it forces people to move stuff to the main tree instead of going the lazy way and putting inter-overlay dependencies. If the concept of "overlay" is taken as "feature overlays", then dependencies should not go beyond the main tree + the overlay itself. -- ~Nirbheek Chauhan
