Current layman ebuilds all contain the line keepdir /usr/local/portage/layman which always messes with my main portage-overlay that resides in /usr/local/portage and which is used as my main source to spread my overlay over every machine via rsync that I have to administer. With each update of layman I have to remove /usr/local/portage/layman/.keep_app-portage_layman-0 /usr/local/portage/layman after the update. I've always considered /usr/local being safe from changes done by the package-manager. Isn't there some policy that all stuff portage messes with has to go to /usr (or /opt for binary-only stuff) instead of /usr/local? Reproducible: Always Steps to Reproduce:
Reassigning to maintainer.
Isn't it /usr/portage/local/layman nowadays?
It was in 1.1.1, but it moved in 1.2.3: layman-1.1.1.ebuild: elog "source /usr/portage/local/layman/make.conf" layman-1.2.3.ebuild: elog "source /usr/local/portage/layman/make.conf"
The complaint makes sense to me. The problem with the old location was that /usr/portage is really the domain of portage and layman should not install anything there. I don't think it makes sense to switch the location yet again. /usr/local/portage seems fine to me in general. So I guess I'm left with removing the "keepdir" line. The user will have to create that location himself. Would that be okay? Maybe I just add an option "setup" to layman that will give users a shortcut to the layman default setup. I could package adding the line to /etc/make.conf there, too.
As long as I can prevent the layman ebuilds to add content into /usr/local/layman I am perfectly fine with whatever you plan to implement as fix.
Sorry, I mean /usr/local/portage of course (stupid me *sigh*)
Moved default to /var/lib/layman upstream, closing. http://layman.git.sourceforge.net/git/gitweb.cgi?p=layman/layman;a=commitdiff;h=218e6a12ceb1808e0f5544eaec933e1172762551
