Re: [SuSE Linux] .tgz versus .tar.gz?
At 07:55 11.11.98 +0100, you wrote:
Well, an other one... easy for some I believe but confusing for me. What is the differance? Most packages you find around is packed .tar.gz, but if you wanna use Yast to install or update a package not prepared by suse yet, Yast just support .rpm (hardly found anywere) and .tgz (hard to find as well), so how to do if you wanna use yast and the package only is found as .tar.gz?
.rpm files are packages in the "Redhat Package Manager" format, which has been adopted by among others Suse. All .tgz files I have dealt with were normall gnuzip compressed tar archives, which means that the only difference betwenn foobar.tar.gz and foobar.tgz is that the .tgz file name fits inside the DOS 8.3 name space. For the simple some perverse reason that most people who installed slackware and other early distributions mainly ran som variety of DOS, this name truncation was necessary in the early days. - Peter -- Peter N. M. Hansteen peter@datadok.no <A HREF="http://www.datadok.no"><A HREF="http://www.datadok.no</A">http://www.datadok.no</A</A>> Datadokumentasjon A/S, Bredsgaarden 2, N-5003 Bergen, Norway Tel: +47 55 32 08 02 Fax: +47 55 32 14 95 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
So by that mean you can simply rename a foo.tar.gz to foo.tgz to make it installable with YaST, is that right? Joakim "Peter N. M. Hansteen" wrote:
At 07:55 11.11.98 +0100, you wrote:
Well, an other one... easy for some I believe but confusing for me. What is the differance? Most packages you find around is packed .tar.gz, but if you wanna use Yast to install or update a package not prepared by suse yet, Yast just support .rpm (hardly found anywere) and .tgz (hard to find as well), so how to do if you wanna use yast and the package only is found as .tar.gz?
..rpm files are packages in the "Redhat Package Manager" format, which has been adopted by among others Suse. All .tgz files I have dealt with were normall gnuzip compressed tar archives, which means that the only difference betwenn foobar.tar.gz and foobar.tgz is that the .tgz file name fits inside the DOS 8.3 name space. For the simple some perverse reason that most people who installed slackware and other early distributions mainly ran som variety of DOS, this name truncation was necessary in the early days.
- Peter -- Peter N. M. Hansteen peter@datadok.no <A HREF="http://www.datadok.no"><A HREF="http://www.datadok.no</A">http://www.datadok.no</A</A>> Datadokumentasjon A/S, Bredsgaarden 2, N-5003 Bergen, Norway Tel: +47 55 32 08 02 Fax: +47 55 32 14 95 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Wed, 11 Nov 1998, Joakim Schramm wrote:
So by that mean you can simply rename a foo.tar.gz to foo.tgz to make it installable with YaST, is that right?
Hold it. You cannot simply install every tar.gz-File, it depends on what is included an which directory structure it has. Most of the time, targzs contain the sources for a program. Before you can use it, you have to configure and compile it. Some simple commands: tar ztvf <filename.tar.gz/.tgz> - list the content of a tgz-File tar zxvf <filename> - extract it (including subdirs) Most source packages contain a README and a INSTALL file. Read them carefully! Bye, LenZ ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi thanks for answer... Lenz Grimmer wrote:
Hold it. You cannot simply install every tar.gz-File, it depends on what is included an which directory structure it has. Most of the time, targzs contain the sources for a program. Before you can use it, you have to configure and compile it. Some simple commands:
Well, I understand I can't just take anything, I was more conserned regarding file format, as YaST don't (for some reason) take .tar.gz. As I now have chosed SuSE as my distrib with YaST and RPM support, I also want to use it... of cause I can go the old path, but thats not realy what I want to do. If there is no .rpm available, but an updated release in .gz (which still seams to be most usual) I would like create one, instead of waiting for it eventually become available... that way I can maintain to keep my installation tidy and userfreindly. I guess thats the purpose with RPM, or? So, how can I go on to convert a .gz package to a .rpm? Alien is obviously a tool handy in the situation, but it don't seams enough just to do a "alien --to-rpm <package.tar.gz/.tgz> I tried with both proftpd1.2.0.pre1.tar.gz (renamed to .tgz) and apache 1.3.3. Yast noticed that I had an other (CD orginal) version installed and replaced it, but ftp didn't work anymore after. The new proftpd was placed otherwere and orginal was deleted. Probably some path or something was set differently by alien. YaST didn't notice I had an other version of apache instaled though. I guess I can go ahead and find things out on my own, but a few lines of direction would be great and highly appreciated. The once below is probably one step, but I don't want install that way, as it seams to bring the info of my installation out of step, causing a lot of extra work to bring it in and aline with the rest. Better use that time to work on something that can come to use for others as well. Sharing with other words. With that I would like to put my vote on what someone said about a contrib directory... Thanks to Peter as well for bothering with my problem. Joakim
tar ztvf <filename.tar.gz/.tgz> - list the content of a tgz-File tar zxvf <filename> - extract it (including subdirs)
Most source packages contain a README and a INSTALL file. Read them carefully!
Bye, LenZ
------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Wed, 11 Nov 1998, Joakim Schramm wrote:
Hi thanks for answer...
Never mind. :)
Well, I understand I can't just take anything, I was more conserned regarding file format, as YaST don't (for some reason) take .tar.gz.
Thanks for the hint.
As I now have chosed SuSE as my distrib with YaST and RPM support, I also want to use it... of cause I can go the old path, but thats not realy what I want to do. If there is no .rpm available, but an updated release in .gz (which still seams to be most usual) I would like create one, instead of waiting for it eventually become available... that way I can maintain to keep my installation tidy and userfreindly. I guess thats the purpose with RPM, or?
It is, indeed.
So, how can I go on to convert a .gz package to a .rpm? Alien is obviously a tool handy in the situation, but it don't seams enough just to do a "alien --to-rpm <package.tar.gz/.tgz>
That's also true.
I tried with both proftpd1.2.0.pre1.tar.gz (renamed to .tgz) and apache 1.3.3. Yast noticed that I had an other (CD orginal) version installed and replaced it, but ftp didn't work anymore after. The new proftpd was placed otherwere and orginal was deleted. Probably some path or something was set differently by alien. YaST didn't notice I had an other version of apache instaled though.
Wow, you are adventorous. I suspect, that you now have installed source files instead of the precompiles binaries from the original RPM.
I guess I can go ahead and find things out on my own, but a few lines of direction would be great and highly appreciated. The once below is probably one step, but I don't want install that way, as it seams to bring the info of my installation out of step, causing a lot of extra work to bring it in and aline with the rest. Better use that time to work on something that can come to use for others as well. Sharing with other words. With that I would like to put my vote on what someone said about a contrib directory...
Check the RPM-HOWTO (thanks, Donnie!) for a quick intro on how to build packages. Most tar.gz-Files today only contain the sources and you have to compile them on your own. It makes no sense to install a source package with YaST... The capability of YaST to install tgz-Archives is a leftover from ancient times, when tgzs where the way of distributing binaries... Bye, LenZ ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Lenz Grimmer wrote:
Wow, you are adventorous. I suspect, that you now have installed source files instead of the precompiles binaries from the original RPM.
Hi and thanks for response, but just some to cool your nerves while I going throug it all. I have an extra box which is just experimental, for praktical reasons... so I don't mess up some of the real stuff. So don't worry, it's just that life is short :) Joakim - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 11 Nov 1998, Lenz Grimmer wrote:
Check the RPM-HOWTO (thanks, Donnie!) for a quick intro on how to build packages. Most tar.gz-Files today only contain the sources and you have to compile them on your own. It makes no sense to install a source package with YaST... The capability of YaST to install tgz-Archives is a leftover from ancient times, when tgzs where the way of distributing binaries...
Bye, LenZ Leftover from the days, where Slakware was considered a major distribution instead of the dinosauric hacker's toy ( no database, very raw installation routine and program management ) that it seems to be viewed as today?
-M - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 11 Nov 1998, Joakim Schramm wrote:
So, how can I go on to convert a .gz package to a .rpm? Alien is obviously a tool handy in the situation, but it don't seams enough just to do a "alien --to-rpm <package.tar.gz/.tgz>
Alien has it's uses, but it's primarily for converting packages that are ready to rock and roll, form one distribution format to another. It doesn't have anything to do with taking tar.gz files of pure sources and converting them to rpms, debs, slps or whatever. See below. (Note: slakware tar.gz might be the basis of confusion because they aren't normal tar balls of sources and have some things added to them so that you can go 'installpkg blah.tar.gz'and have a running program. Maybe this is where the confusion is.) The easiest way to do what I think you want to do,or at least the one I use, is to build my own rpms. All you really need is the sources ( the .tar.gz ) and a spec file. There's an RPM How-To that comes with the distribution in the docs packages that clearly tells you how to do it. It's pretty easy. The rpm man page is really helpful too. Basically ( a bit oversimplified ) on S.u.S.E. there's a /usr/src/packages dir, with BUILD, RPMS, SOURCES, SPECS, and SRPMS directories in them. You can put sources in SOURCES ( the process will even unzip them for you if I remember right ) and write a spec in SPECS and if named blah.spec and it's written right ( look at an available spec file to get a basic template notion) just go rpm -ba blah.spec and you can sit there and watch the process. It'll leave and RPMS ( usually in /usr/src/packages/RPMS/i386 ) and a SRPM in /usr/src/packages/SRPMS,etc etc. You can then install the RPM with rpm -Uvh or whatever onto your system. If you have an SRPM and you 'install' it it'll already put in the sources and spec etc in the right directory on S.u.S.E. and all you have to do is check out the spec file in <...>/SPECS and make sure it doesn't look funky for your system. If it's groovy or after you get done making the right adjustments, just proceed to build it and woolah, you have a shiny, freshly built rpm, ready to rock.
I tried with both proftpd1.2.0.pre1.tar.gz (renamed to .tgz) and apache 1.3.3. Yast noticed that I had an other (CD orginal) version installed and replaced it, but ftp didn't work anymore after. The new proftpd was placed otherwere and orginal was deleted. Probably some path or something was set differently by alien. YaST didn't notice I had an other version of apache instaled though.
If you built from sources YaST would have no reason TO recognize it. I think all YaST does it query the rpmdb.
Most source packages contain a README and a INSTALL file. Read them carefully!
Bye, LenZ
-M - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Thanks for the good information... Now I have all I need... except time ;) but that will come as well. Joakim Michael Johnson wrote:
On Wed, 11 Nov 1998, Joakim Schramm wrote:
So, how can I go on to convert a .gz package to a .rpm? Alien is obviously a tool handy in the situation, but it don't seams enough just to do a "alien --to-rpm <package.tar.gz/.tgz>
Alien has it's uses, but it's primarily for converting packages that are ready to rock and roll, form one distribution format to another. It doesn't have anything to do with taking tar.gz files of pure sources and converting them to rpms, debs, slps or whatever. See below. (Note: slakware tar.gz might be the basis of confusion because they aren't normal tar balls of sources and have some things added to them so that you can go 'installpkg blah.tar.gz'and have a running program. Maybe this is where the confusion is.)
The easiest way to do what I think you want to do,or at least the one I use, is to build my own rpms. All you really need is the sources ( the .tar.gz ) and a spec file. There's an RPM How-To that comes with the distribution in the docs packages that clearly tells you how to do it. It's pretty easy. The rpm man page is really helpful too. Basically ( a bit oversimplified ) on S.u.S.E. there's a /usr/src/packages dir, with BUILD, RPMS, SOURCES, SPECS, and SRPMS directories in them. You can put sources in SOURCES ( the process will even unzip them for you if I remember right ) and write a spec in SPECS and if named blah.spec and it's written right ( look at an available spec file to get a basic template notion) just go rpm -ba blah.spec and you can sit there and watch the process. It'll leave and RPMS ( usually in /usr/src/packages/RPMS/i386 ) and a SRPM in /usr/src/packages/SRPMS,etc etc. You can then install the RPM with rpm -Uvh or whatever onto your system. If you have an SRPM and you 'install' it it'll already put in the sources and spec etc in the right directory on S.u.S.E. and all you have to do is check out the spec file in <...>/SPECS and make sure it doesn't look funky for your system. If it's groovy or after you get done making the right adjustments, just proceed to build it and woolah, you have a shiny, freshly built rpm, ready to rock.
I tried with both proftpd1.2.0.pre1.tar.gz (renamed to .tgz) and apache 1.3.3. Yast noticed that I had an other (CD orginal) version installed and replaced it, but ftp didn't work anymore after. The new proftpd was placed otherwere and orginal was deleted. Probably some path or something was set differently by alien. YaST didn't notice I had an other version of apache instaled though.
If you built from sources YaST would have no reason TO recognize it. I think all YaST does it query the rpmdb.
Most source packages contain a README and a INSTALL file. Read them carefully!
Bye, LenZ
-M
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
grimmer＠suse.de -
hekate＠intergate.bc.ca -
josch57＠geocities.com -
peter＠datadok.no