I agree w/ pretty much everything said below and would also like to see a DESTDIR-branch. I'd add the uninstall commands should also be broken out into pre- and post- stages. An example would be calling pwunconv and grpunconv if you uninstall shadow - they need to be executed before removing the shadow package.
On Mon, Mar 31, 2008 at 11:31 AM, Sukucorp Sukucorp <[EMAIL PROTECTED]> wrote: > I most certainly would vote for a branch with the DESTDIR style of > installation. I am already in the process creating a PM for my > purposes. If somebody is interested, check out my scripts at > <http://anduin.linuxfromscratch.org/~tushar/downloads/>. They are > still a WiP. I am planning to create an online presence for the PM at > <http://ttpm.sarovar.org/>. > > Given that there are so many personal preferences, IMO including a PM > in the book is not prudent. But what the book can probably include is > to have commands to install the pkg into DESTDIR. A typical pkg page > in the book would be as follows: > * Prepare Source commands > * Compile commands > * Test pkg commands > * Install pkg into DESTDIR commands > * Pre Relocation commands > * Post Relocation commands > * Uninstall commands. > > The general page that explains how to unpack the source would also > include how to relocate the source from DESTDIR to /. > > Someone who does not want to use a package manager would just use the > commands in the book as is and even without a PM, would get the > following features: > * Allow upgrade of libraries in use. > * Ability to figure out what the package includes before installing it > and to prevent relocation if something goes wrong during the > installation. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
