Rick Moen wrote:
Works well enough if the source packages reliably furnish functional
"remove" targets (or equivalent) in their Makefile structure. Last time
I tried the Slackware approach, that wasn't the case, but things may
have changed.
Umm... this is not necessary. removepkg remembers and removes
everything installpkg put in. There is no need for a Makefile
remove target to be present, and besides you'd really rather
not have to depend on that.
I _always_ make my own packages from source and install from
that. That's the most foolproof way to ensure clean uninstalls.
Just remember to confirm, by doing a quick scan of the output of
make install, that all files end up in the package creation
directory (i.e. /pkgcreate) as a few install scripts have bugs
where even if you specify make install PREFIX=/pkgcreate/usr/local,
it will put some files under /usr/local instead - these can be
detected as they invariably show up in the output of make install.
Try building new releases of XFree86 or glibc from source. ;->
Thankfully, Volkerding and gang do that for you... =) I did
find the gcc 2.95 to gcc 3.1 upgrade from DIY package experience
for my Slackware 8.1 setup unexpectedly problem-free.
Later when I manually upgraded to 9.0, I removed my DIY gcc 3.1
packages and went with the 9.0 ones. Again, the whole thing went
smoothly.
--
Philippine Linux Users' Group (PLUG) Mailing List
[EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
Official Website: http://plug.linux.org.ph
Searchable Archives: http://marc.free.net.ph
.
To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
.
Are you a Linux newbie? To join the newbie list, go to
http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
