On 09/12/13 01:00, Alan McKinnon wrote: > Yes of course, it make a great deal of sense now. Basically, your local > overlay had no idea where the parent portage tree is or how to find it > so couldn't find the eclass directory. > > As I understand it, this information used to be hard-coded magic and > overlays would "just know where to look". Since recently, you have to > configure it explicitly and not use hidden super-magic. > > You would have been getting confusing messages in emerge output about a > faulty masters setting for overlays, pity we didn't spot that up front. > Double pity that there wasn't a clear message or news item about what > the error meant and the impact....
Thanks, Alan, for the great help! SAMBA is now up and running with my custom changes... -- Timur
