Enable bash-completion in bash_profile

[pkgusr] / README

-*- mode:text; eval:(footnote-balloons) -*-
Time-stamp: <Saturday Mar  8, 2014 17:30:08 steve>

Introduction:
============

Here are the tools I use for package management on bastard.  It is
based _very_ heavily on the LFS hint:

  "More control and package management using package users (v1.4)"

Which I have included in this repo (see LFS-pkgusr-hint.txt) and is
considered essential reading.

The main differences (enhancements?) these tools have over the
original LFS hint are:

         o A set of convenience shell functions for pkg users, and a
           pseudo "master installer"[1]

         o Make it easy to give individual settings to each pkg user.
           For example, some pkg users may need ssh/gnupg or $DISPLAY
           set. 

         o Better build script and .project templates

           As of v1.4 of the hint, Matt uses a central build script
           and each pkgusr has a "build.conf"... an interesting idea
           and I may switch to that method one day, but for now I use
           a build script for each pkgusr.

         o Better uninstall script.

         o Most of the "wrapper" scripts have been updated or
           rewritten.

         o Includes a `which' script.

         o Includes a `/bin/mail' script.

         o Includes a `lesspipe.sh' script (unashamedly stolen from
           Pat Volkerding and Slackware.  Thanks, Pat!)

         o A more complete list of "install" directories.
           Everyone's needs and tastes are different so not everything
           I have in my list of install directories you'll want.  Edit
           it to suit you.

         o Includes an elisp library that implements much of the
           convenience shell functions. [2]

         o Allow pkgusr to run ldconfig as root safely via a wrapper
           script and sudo.

           Matt uses a setuid C wrapper that calls execve(2) to do
           this.  Which, IMO, is not the right way to go.  
           

You should understand that not everything here can be used straight away.
The /bin/mail script, for example, needs Zsh, and Sendmail installed
(could probably be rewritten to use bash with very little effort); the
ldconfig wrapper needs sudo; if you want to set yourself up as a "master
installer", OpenSSL and OpenSSH are needed; and pkgusr.el needs SXEmacs
(or XEmacs/Emacs) obviously.

FHS Note:
========

As of 2021-02-06 I have switched over to following the current FHS
policy that states /bin /sbin /lib /lib64 should all be symlinks into
/usr.  This conflicts with a lot of the {B,}LFS build/install
instructions that have you move libraries and other binaries into /lib
/bin /sbin etc.  You pretty much just gotta ignore that shit and embrace
2021... we have cookies!

Pre-Installation:
================

  1.  Install bison, flex, nano, and less (in that order) into your
      /tools dir.  Bison, and flex are needed to build binutils in the
      chroot.  And nano and less make life for the package user so
      much easier.

      As of LFS SVN-20140303, they still do not install bison and
      flex in chapter 5.  I think it might be because they install
      the binutils from gnu (eww), whereas I install the _proper_
      optimised for Linux binutils from kernel.org which requires
      bison/flex.  It is also odd that in chapter 6 when they do
      install these 2 packages, they do them in the wrong order
      (bison should be done before flex).

  2.  At the point in the book where it has you mount the devpts
      filesystem, it neglects to mention that you have to specify a
      mode and gid:
           mount -vt devpts devpts ${LFS}/dev/pts -o gid=5,mode=620

      Update:  I think LFS has this now, but check anyway.

  3.  Install sudo into your /tools dir.  Sudo is used to let pkgusrs
      run ldconfig as root, thereby bypassing the annoyance of getting
      errors about /etc/ld.so.cache not being able to be updated.

      I don't have a LFS build chain anymore so I am not 100% certain
      if this is possible, but I cannot think of any reasons why it
      shouldn't be.  Let me know if you have an issue with this step.

  4.  When creating the initial /etc/group file, I don't use the LFS
      book suggestions.  I have my own set groups that I've been using
      since 1995, and old habits are so hard to break. :-)

      Anyhoo, here's my initial group file...

cat>/etc/group<<EOF
root:x:0:
bin:x:1:
daemon:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mem:x:8:
kmem:x:9:
wheel:x:10:
floppy:x:11:
mail:x:12:
news:x:13:
uucp:x:14:
man:x:15:
dialout:x:16:
audio:x:17:
video:x:18:
cdrom:x:19:
games:x:20:
utmp:x:22:
usb:x:23:
tape:x:26:
nobody:x:98:
nogroup:x:99:
users:x:1000:
EOF

Installation:
============

Step 1... Go read that LFS hint.  You'll probably want to read it
through a couple of times.

Step 2... Don't follow the instructions in the LFS hint for how to set
things up and where to dump the scripts etc.  Instead see the next
section, "Pkgusr Specific Installation".

Pkgusr Specific Installation
============================

In the hint it tells you how where and when to put the helper scripts and
stuff, which is great, but I have not included the "more-control-scripts"
tarball in this repo.  I've rewritten/tweaked most of the scripts and
split them out into their respective directories so that I can easily
modify and track them.  Because of that you may get a little lost in
aligning what the hint says to the files you have in this repo.

When
----
Right _BEFORE_ installing linux libc headers at start of Chap 6 in the
LFS book.

Where
-----
From _OUTSIDE_ the chroot environment

Who
---
Do this as root

How
---
Copy'n'Paste Fun!

PKGUSR=/path/to/your/pkgusr/repo/working/dir &&  ## Yeah, edit this bit!
cp -va ${PKGUSR}/etc/pkgusr ${LFS}/etc &&
chown -vR 0:0 ${LFS}/etc/pkgusr &&
install -vm711 -o0 -g0 -d ${LFS}/etc/sudoers.d &&
install -vm440 -o0 -g0 ${PKGUSR}/etc/sudoers.d/99-pkgusr \
    ${LFS}/etc/sudoers.d &&
install -vm644 ${PKGUSR}/installdir.lst ${LFS}/root &&
install -vm755 ${PKGUSR}/bin/{which,mail} ${LFS}/usr/bin &&
install -vm755 ${PKGUSR}/usr/bin/* ${LFS}/usr/bin &&
install -vm750 -o0 -g9999 -d ${LFS}/usr/lib/pkgusr &&
install -vm550 -o0 -g9999 ${PKGUSR}/usr/lib/pkgusr/* \
    ${LFS}/usr/lib/pkgusr &&
install -vm755 ${PKGUSR}/usr/sbin/{add_package_user,install_package} \
    ${LFS}/usr/sbin &&
install -vm755 ${PKGUSR}/usr/sbin/{group,user}add ${LFS}/tools/bin &&
unset PKGUSR

From this point on you need to re-enter the chroot environment.  So
these next (and final) steps are done _INSIDE_ the chroot (as root).

Create the install group:
------------------------

groupadd -g 9999 install


Set up the install directories:
------------------------------
(you did peruse and edit this list getting rid of things you know for
sure you won't need, didn't you?)

while read dir; do
    if [ ! -d ${dir} ]; then
        install -v -m1775 -o0 -g9999 -d ${dir}
    fi
done < /root/installdir.lst

One last symlink:
----------------

  ln -sv /tools/lib/libncurses.so.5 /usr/lib/libncursesw.so.5

(don't forget you'll have to remove that before you install ncurses
later)

Alright, where are we up to now?  Well, in the LFS hint you are up to:

  7.2 Walkthrough: Installing linux-libc-headers

And in the LFS book, you are up to:

  6.7. Linux-3.13.5 API Headers

So have fun building the rest of your LFS system!


Footnotes: 
[1]  The "master installer" is just someone who can change their
     identity to a pkg user.  It _could_ be root, though I don't
     recommend it.  I use a ssh->root->su->pkgusr from my personal A/C
     which is a single "step" (I'm not stopping in a root shell).

[2]  pkgusr.el is probably fairly SXEmacs-centric, but should work
     with perhaps minor changes on XEmacs or even GNU/Emacs.