I'd like to discuss what should be default directory for repos/overlays. Momentally is used /var/lib/layman, because layman. When we migrate to repos.conf, there should be some recommended location, where place overlays. I'd propose /var/lib/overlays . Any ideas, suggestions? Thank you Reproducible: Always
(In reply to David Heidelberger (okias) from comment #0) > Momentally is used /var/lib/layman, because layman. When we migrate to > repos.conf, there should be some recommended location, where place overlays. What does repos.conf change here? It's just a different way the configure repositories than PORTDIR and PORTDIR_OVERLAY. I don't think layman is going away, so most overlays will stay there anyway. > I'd propose /var/lib/overlays . > Any ideas, suggestions? > How should we encourage people to use that?
Layman can be configured to install anywhere in the filesystem. There is going to be a change in the default tree location. There is a whole big bikeshed thread in the -dev mail list a little more than a year ago. They couldn't decide where exactly it should be in /var. That said. It is closer to becoming a reality. One of the biggest hurdles to moving the default location has been catalyst which produces the stages. I have been re-writing catalyst's code to make it easily configurable. Once the new code is in use producing stages for everyone's use. The tree move can happen. I'll see what happens then. Also this seems more like a layman bug than a portage one. I do both, so... I do need to migrate layman to the repos.conf format. But I'll probably wait a bit longer and incorporate the new sync system we're developing in portage to be done. Then layman overlays can be synced via emerge --sync if configured for it. While still being managed otherwise by layman.
I plan prepare script for layman => repos.conf migration. I'll poke you when it will be done. (In reply to Brian Dolbec from comment #2) > Layman can be configured to install anywhere in the filesystem. > > There is going to be a change in the default tree location. There is a whole > big bikeshed thread in the -dev mail list a little more than a year ago. > They couldn't decide where exactly it should be in /var. > > That said. It is closer to becoming a reality. One of the biggest hurdles > to moving the default location has been catalyst which produces the stages. > I have been re-writing catalyst's code to make it easily configurable. Once > the new code is in use producing stages for everyone's use. The tree move > can happen. > > I'll see what happens then. > > Also this seems more like a layman bug than a portage one. I do both, so... > I do need to migrate layman to the repos.conf format. But I'll probably > wait a bit longer and incorporate the new sync system we're developing in > portage to be done. Then layman overlays can be synced via emerge --sync if > configured for it. While still being managed otherwise by layman.
The layman-9999 ebuild can handle repos.conf configuration when installing new ebuilds. However, I'll leave this open until we get a new release.
layman-2.1.0 adds repos.conf support. A known bug is that it currently doesn't check to see if the repos.conf exists prior to writing to it, and this will cause issues. So be sure to create the repos.conf file (default location: /etc/portage/repos.conf/layman.conf) prior to attempting to use the repos.conf functionality. This bug will be fixed in the next release, which should be within the next month.
