Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-30-2002, 05:56 AM
|
#1
|
LQ Newbie
Registered: Apr 2002
Distribution: RedHat 8.0, FreeBSD 4.8
Posts: 12
Rep:
|
Building RPM files from TAR files
My system doesn't seem to want to run newer Linux versions than RedHat 7.0, or Mandrake 7.2 (based on 2.2 kernel), due to a strange SCSI setup.
For the most part, this doesn't leave me really crippled, since I can get source RPMs and they compile fairly easily, and the same goes with source tarballs. For ease in archiving, I'd like to be able to build binary and source RPMs out of the tarballs. My experience has been more misses than hits in using the command: rpm -ta to build the binary RPMs. Typically, RPM reports back that the following fields are missing from the main package and refuses to proceed:
Name, Version, Release, Summary, Group, and License.
How are these fields added, and what syntax on RPM should I use?
|
|
|
04-30-2002, 01:41 PM
|
#2
|
Senior Member
Registered: Nov 2001
Location: Wa. State
Distribution: Slackware
Posts: 1,261
Rep:
|
Look into using the alien program to just convert the tarball to an rpm.
|
|
|
05-01-2002, 12:07 PM
|
#3
|
Member
Registered: Apr 2001
Location: chicago, IL
Distribution: debian, redhat
Posts: 280
Rep:
|
makes rpms, debs or slack tarballs out of source: look over there ->
http://asic-linux.com.mx/~izto/checkinstall/
|
|
|
05-05-2002, 11:02 PM
|
#4
|
LQ Newbie
Registered: Apr 2002
Distribution: RedHat 8.0, FreeBSD 4.8
Posts: 12
Original Poster
Rep:
|
Solution tried and works well.
The solution of using CheckInstall was what I was looking for. Tested it, and it works great. Many Thanks!
I tried Alien, and it works, but is a bit slow. Might be better on binaries, tho.
Many thanks!
|
|
|
All times are GMT -5. The time now is 02:33 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|