Originally posted by Nu-Bee
Thanks, this is what I was looking for.
1) What happens if one installs the tarball then a dependency is missing,
2) or a file it is dependent on is of the wrong version?
3) Am I correct in thinking that *make* will make an RPM that one can install via RPM...and then it will be listed in the database?
I am trying to decide which way to settle on...
1: IF you just have a tarball, and not a slackpack, it doesn't
always make sense to talk about "installing" a tarball. If you
happen to have a tarball that was made from a bunch of files that
are all full pathnames, then that could be considered installing.
If our system is missing something that package is dependent on,
then the package won't work, and you'll get some sort of a crash
at runtime. If just have an archive that's been compressed, when
you untar/ungzip it, it'll just be an untared/ungziped bunch of
files. The Slackware package manager doesn't know how to
check for dependencies, but you can certainly have the
setup/install script check for you. . .
2: Same as above.
3: You can use rpm to roll your own RPM packages. Packaging
up some files doesn't add those files to an rpm "database", that
should happen when you unpack them. The "database" only
really exists on your system, there isn't a central place that
rpm reports to and registers your rpm package. You should
really read the rpm man page, and then follow the link to the rpm
web site (http://www.rpm.org
Are you packaging something up yourself? Are you terribly
worried about dependency checking? Do you want something
that can be dealt with on many different platforms? *I* can't
stand the way rpm (doesn't) work(s), so I would never
recommend it to anyone, but you should seek a second opinion.
If you are really concerned, do both. . .