On Wed, 27 Feb 2019 at 23:44, Ken Moffat via lfs-dev <[email protected]> wrote: > > On Wed, Feb 27, 2019 at 06:05:28AM -0800, Mark Wigzell via lfs-dev wrote: > > I am using the package management scripts in more_control_helpers. > > One of the issues with that is that many of those packages using the "info" > > mechanism try to update /usr/share/info/dir and fail because of no > > permission. > > ... > > > > Any pointers? > > > > --Mark > > If you don't get any useful replies here (I suspect most people > here don't use that method, but perhaps somebody does) I suggest you > ask on -support. > > From past questions on -support, the hint seems to have caused a lot > of problems. But it might be that the successful users never > subscribe to that list. > > chmod 666 might be ok for LFS itself, but not good for afterwards. > > ĸen
Only just noticed this when perusing the archives: might have benefited from a "PkgUser" term in the subject. Anyroad, I do use that method, indeed am in the process of installing 8.4 using it, along with (finally) providing (somewhere) a rendered book and/or some SVN patches to go along with the Multilib patch. I have found that the PkgUser build has often shown up things that the standard LFS book, where root just does everything, and so may do things that you don't necessarily notice, of which the clobbering of files is a case in point. Here, for what they are worth are my thoughts on Mark's issue: The original "more_control" was written some time ago now and so, you will find that what the hint suggets will be "install directories", and so which will be given 775 permissions and be owned by the "install" group, of which all of the "package" usernames are members, is outdated. Trouble is, as things have moved on, some of the original "install directories" no longer appear in an LFS build; some new directories, that should be considered to be "install directories", have appeared in an LFS build, and one or two existing directories that weren't considerd to be "install directories" before, should now be, as a result of packages doing different things during their install. One or two files also fall into the same category, as well as the issue of there being some links created in Chapter 5 that a Chapter 6 PkgUser will try and overwite with a real file that it, the PkgUser "owns", but then finds that it can't remove the link. Clearly fixable but confusing if you don;t know about it. My suggestion would therefore be to alter any directory with which you are having issues to be chgrp install; chmod g+w,t and for any files to be made chgrp install; chmod g+w. so 664, not your 666. Not clear to me that any "install files" need to be o+w (666) because it should only be package usernames that should be allowed to update them. I will check what the perms were on my 8.3 PkgUser build and follow up. HTH, Kevin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
