Bob Proulx wrote, on 12. mar 2007 05:29:
[...]
-If you make a simple spec file, which basically just unpacks the tar.gz
file and doesn't config or build anything, where does it unpack to?
To whichever %_topdir/BUILD directory one has in one's ~/.rpmmacros
(defaults to an unmentionable that isn't writable by mortals and thus
encourages root builds, which are an anathema).
As a consumer of some commercial rpms I really despise vendors that
try to do that. I usually end up repackaging the rpm.
If you create an rpm that simply transports the files and then your
'%post' script moves it around then what good is putting it into an
rpm? None whatsoever. Better not to hide what you are doing and
instead simply give your users a tar.gz file to unpack instead.
Heaven help us, no. An example is the Mozilla.org Firefox latest 2.0.0.2
tar.gz on RHAS/RHEL4. This /can/ get untarred to /usr/local, in which
case one has a competing alternative to Red Hat's standard FF 1.5 and
can exist alongside it, BUT. If one does that, one defeats the whole
update (up2date, yum) philosopy. One has no plugins or other standard
stuff, all as to be done by hand. Far better, if one is committed to
using 2.0.2 is to write/purloin a spec that will replace 1.5 with
2.0.0.2 including icons, multiple plugins and a gang of other requisites.
Another example might be an rpm that doesn't do anything other than
installing scripts - doesn't do any builds at all. If ever an update
came, there would be no record in the rpm DB.
RPMs seem like the best way to keep version control, especially because
it's such a widespread protocol.
tar.gz files are even more widespread and popular. :-)
I used to think like that before I got into serious sysadminning (even
you don't really think that, you're just provoking), but installing
often highly dependent stuff and configuring it on multiple systems with
a myriad of custom-written configuration scripts calls for versioning
and I haven't found anything better than rpm yet (old SCO, Novell
UnixWare, SGI and Solaris admin).
--Tonni
--
Tony Earnshaw
Email: tonni at hetnet dot nl
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
