> This isn't a problem for Slackware packages because the packages themselves
> usually contain all the libraries and support files that the package
> needs. If
> you've never created a Slackware package before the process is: download the
> source, compile, make with a target directory pointing to a temp package
> directory which "installs" everything with the correct structure to this temp
> package directory. When the package is then created, everything the package
> needs is bundled along with the slackdesc file.
What? You mean a copy of Gtk+ is included with every gtk app?!
> Slackware's package mantainers are very good to include any libraries
> that your
> software may need since having unresolved library dependencies sucks. I guess
> this is the main difference between everything else and TGZ's. It's not much
> of a "package" if it doesn't contain everything it needs, is it? Kind of like
> buying a car but having to make separate trips to the tire store, seat store,
> windshield store... common components for a car, but they are usually
> *packaged* together. (what a concept!)
So...every time I buy a tire, I have to buy the rest of the car too?
-- Tcsh: Now with higher FPS! http://www.gnu.org/philosophy/no-word-attachments.html----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:35:57 EDT