ZINF - zinf is not freeamp
Hi all. I decided to install the lastest version of ZiNF rather than the version of freeamp that comes with 8.2. I have three options. One is to use rpms built for RH 8.x/9. The question regarding this is that there are seperate packages involved. id3lib, libmusicbrainz, zinf, znif-arts, zinf-cobra, zinf-esd, zinf-extras, and zinf-vorbis. I am unsure if this will be problematic since I'm no sure about difference between SuSE libs and otherthings being placed in whatever dir will be a problem later, but the upside is that the rpm database will know about them and that makes other maintenance issues easier. Furthermore, new in 8.2 is a complete set of (mirrored for lack of a better description) set of dirs/subdirs in the /usr/local that has most sys folders. [Side Note: I was pleasantly surprise to look in the /usr/local to include the following: bin dev games include man mnt proc sbin src success usr windows boot etc home lib media opt root share srv tmp var and these are fully functional as is that under the "/" directory] Two get the aforementioned files as *.src.rpms and rebuilid them for my system. But, Is the rpm database going to correctly reconized these later so that I can track them correctly with rpm? Three is to get the source packages and then create my own rpms for SuSE 8.2 myself. I haven't done this but feels it's time I learned to. If I were to take this path I would greatly appreciate any pointers that others may offer, such as specific literature/readme's and programs that would make it easier for an rpm noob to use and follow. My personal feeling is that it may be time for me to take another Linux step and learn to make my own rpms. However, having never done this before so I wanted to get some feedback from those on the list. Is this an o'k set of packages to start with or is this too ambitious and I should perhaps start with something simplier without the extra stuff like the libs, etc, and others? Thanks much in advance. Cheers, Curtis.
On Mon, 12 May 2003 12:00:02 -0700
Curtis Rey
Hi all. I decided to install the lastest version of ZiNF rather than the version of freeamp that comes with 8.2. I have three options.
[....stuff deleted...]
Two get the aforementioned files as *.src.rpms and rebuilid them for my system. But, Is the rpm database going to correctly reconized these later so that I can track them correctly with rpm?
Three is to get the source packages and then create my own rpms for SuSE 8.2 myself. I haven't done this but feels it's time I learned to. If I were to take this path I would greatly appreciate any pointers that others may offer, such as specific literature/readme's and programs that would make it easier for an rpm noob to use and follow.
You can build rpm's from source rpm's, but can I suggest another method. You have a wonderful little program already called "checkinstall" that you can use. You get the compressed tarballs and follow along as though doing a configure/make/make install. However, instead of doing make install you call checkinstall. It actually does the make install for you but then it interactively creates an rpm from the detail it gathers doing the install. It then installs the rpm. This creates an entry in the rpm database and you can subsequently treat it as an rpm installation. It makes maintaining non-SuSE specific software a breeze. All the advantages of your own configure plus rpm management. BTW, I usually run SuSEconfig manually after such an install, for good order. Paul. -- Registered Linux User #313850 "Nearly all men can stand adversity, but if you want to test a man's character, give him power." - Abraham Lincoln
On Monday 12 May 2003 15:30, Paul Conn wrote:
On Mon, 12 May 2003 12:00:02 -0700
Curtis Rey
wrote: Hi all. I decided to install the lastest version of ZiNF rather than the version of freeamp that comes with 8.2. I have three options.
[....stuff deleted...]
Two get the aforementioned files as *.src.rpms and rebuilid them for my system. But, Is the rpm database going to correctly reconized these later so that I can track them correctly with rpm?
Three is to get the source packages and then create my own rpms for SuSE 8.2 myself. I haven't done this but feels it's time I learned to. If I were to take this path I would greatly appreciate any pointers that others may offer, such as specific literature/readme's and programs that would make it easier for an rpm noob to use and follow.
You can build rpm's from source rpm's, but can I suggest another method. You have a wonderful little program already called "checkinstall" that you can use. You get the compressed tarballs and follow along as though doing a configure/make/make install. However, instead of doing make install you call checkinstall. It actually does the make install for you but then it interactively creates an rpm from the detail it gathers doing the install. It then installs the rpm. This creates an entry in the rpm database and you can subsequently treat it as an rpm installation.
It makes maintaining non-SuSE specific software a breeze. All the advantages of your own configure plus rpm management. BTW, I usually run SuSEconfig manually after such an install, for good order.
Paul.
Cool, I do remember hearing about this. Also, is the KRPMbuilder a front end for this. I was giving it a look and some pre-defined arguments (fill in the spaces). Are you or anyone else aware of this program and have any opinion one way or the other? The checkinstall sounds very handy though. I have done many tarballs and am faily comfortable with them. I guess what your saying config make to get things straight, deps, paths, etc.. and the run check install - I'll have a look at the man pages. Cheers, Curtis.
On Mon, 12 May 2003 19:41:37 -0700
Curtis Rey
It makes maintaining non-SuSE specific software a breeze. All the advantages of your own configure plus rpm management. BTW, I usually run SuSEconfig manually after such an install, for good order.
Paul.
Cool, I do remember hearing about this. Also, is the KRPMbuilder a front end for this. I was giving it a look and some pre-defined arguments (fill in the spaces). Are you or anyone else aware of this program and have any opinion one way or the other?
The checkinstall sounds very handy though. I have done many tarballs and am faily comfortable with them. I guess what your saying config make to get things straight, deps, paths, etc.. and the run check install - I'll have a look at the man pages.
Cheers, Curtis.
Hi Curtis, No KRPMbuilder is a serarate program altogether. It is a developer tool for creating rpm's from spec files and all that stuff; sorry I'm not a developer so the terminology eludes me. But it has nothing to do with checkinstall. I noticed elsewhere in this thread that you received cautionary advice about if checkinstall goes wrong. That is correct but please don't let that stop you trying it. IMO you can mess up an install in a number of ways and retrieving things can be messy. I always do an essential files backup before I install any new software (particularly non-SuSE specific), so it's fairly safe. BTW, you can always get help on here! :-) Checkinstall just makes life so much easier when installing tarballs and tarballs make it so much easier to make sure files end up where you want them. It is however just an executable script. It resides in /usr/sbin/checkinstall when installed (so is not in ordinary users path). Have a look at it. I actually edited it because I noticed that when it did the rpm install it used the 'force' option. I don't like using that option at any time so I changed it to -Uvh. It all worked ok still. It may not help with this Zinf stuff but definitely give it a go if you install from tarballs. Good luck, Paul. -- Registered Linux User #313850 "Nearly all men can stand adversity, but if you want to test a man's character, give him power." - Abraham Lincoln
On Monday 12 May 2003 23:21, Paul Conn wrote:
On Mon, 12 May 2003 19:41:37 -0700 Curtis Rey
wrote: [....stuff deleted...]
It makes maintaining non-SuSE specific software a breeze. All the advantages of your own configure plus rpm management. BTW, I usually run SuSEconfig manually after such an install, for good order.
Paul.
Cool, I do remember hearing about this. Also, is the KRPMbuilder a front end for this. I was giving it a look and some pre-defined arguments (fill in the spaces). Are you or anyone else aware of this program and have any opinion one way or the other?
The checkinstall sounds very handy though. I have done many tarballs and am faily comfortable with them. I guess what your saying config make to get things straight, deps, paths, etc.. and the run check install - I'll have a look at the man pages.
Cheers, Curtis.
Hi Curtis,
No KRPMbuilder is a serarate program altogether. It is a developer tool for creating rpm's from spec files and all that stuff; sorry I'm not a developer so the terminology eludes me. But it has nothing to do with checkinstall.
I noticed elsewhere in this thread that you received cautionary advice about if checkinstall goes wrong. That is correct but please don't let that stop you trying it. IMO you can mess up an install in a number of ways and retrieving things can be messy. I always do an essential files backup before I install any new software (particularly non-SuSE specific), so it's fairly safe. BTW, you can always get help on here! :-)
Checkinstall just makes life so much easier when installing tarballs and tarballs make it so much easier to make sure files end up where you want them. It is however just an executable script. It resides in /usr/sbin/checkinstall when installed (so is not in ordinary users path). Have a look at it. I actually edited it because I noticed that when it did the rpm install it used the 'force' option. I don't like using that option at any time so I changed it to -Uvh. It all worked ok still.
It may not help with this Zinf stuff but definitely give it a go if you install from tarballs.
Good luck, Paul.
Thanks Paul. I have no real quams about taking chances, since this is a one user machine. I don't like to have to redo things though and I'm always trying to be smart instead of just busy. I think I'll do that (run a couple of tarballs through checkinstall) because I get a little tired of hunting down stuff from tarballs in my sys, but use them a fair amount because many of the programs I like are in that form. Cheers, Curtis. :)
On Mon, 2003-05-12 at 12:00, Curtis Rey wrote:
Hi all. I decided to install the lastest version of ZiNF rather than the version of freeamp that comes with 8.2. I have three options.
One is to use rpms built for RH 8.x/9. The question regarding this is that there are seperate packages involved. id3lib, libmusicbrainz, zinf, znif-arts, zinf-cobra, zinf-esd, zinf-extras, and zinf-vorbis.
They don't work on SuSE unfortuantly.
I am unsure if this will be problematic since I'm no sure about difference between SuSE libs and otherthings being placed in whatever dir will be a problem later, but the upside is that the rpm database will know about them and that makes other maintenance issues easier.
Furthermore, new in 8.2 is a complete set of (mirrored for lack of a better description) set of dirs/subdirs in the /usr/local that has most sys folders. [Side Note: I was pleasantly surprise to look in the /usr/local to include the following: bin dev games include man mnt proc sbin src success usr windows boot etc home lib media opt root share srv tmp var and these are fully functional as is that under the "/" directory]
Two get the aforementioned files as *.src.rpms and rebuilid them for my system. But, Is the rpm database going to correctly reconized these later so that I can track them correctly with rpm?
Three is to get the source packages and then create my own rpms for SuSE 8.2 myself. I haven't done this but feels it's time I learned to. If I were to take this path I would greatly appreciate any pointers that others may offer, such as specific literature/readme's and programs that would make it easier for an rpm noob to use and follow.
My personal feeling is that it may be time for me to take another Linux step and learn to make my own rpms. However, having never done this before so I wanted to get some feedback from those on the list. Is this an o'k set of packages to start with or is this too ambitious and I should perhaps start with something simplier without the extra stuff like the libs, etc, and others?
Checkinstall script can build them pretty easily, but if it goes wrong results can be interesting :). Checkinstall has to be run as root and takes the place of make install in the source. Although, with Zinf I will be very surprised if you get that far. Its undergoing quite a lot of code changes and... *rant* Too many developers are using Debian stable as a development platform, fine about a year ago, but this seems to cause many issues with up to date distro's like SuSE 8.2 *rant*
Thanks much in advance.
Cheers, Curtis.
Matt
Checkinstall script can build them pretty easily, but if it goes wrong results can be interesting :). Checkinstall has to be run as root and takes the place of make install in the source. Although, with Zinf I will be very surprised if you get that far. Its undergoing quite a lot of code changes and...
*rant* Too many developers are using Debian stable as a development platform, fine about a year ago, but this seems to cause many issues with up to date distro's like SuSE 8.2 *rant*
Thanks much in advance.
Cheers, Curtis.
Matt
This is my concern. I want to accomplish two things. One install Zinf (used it in windows and liked it - just an updated FreeAMP without the copyright "AMP" infringing name). The other is to make rpms for tarballs so the are set to SuSE environ and are in the data base (and to start more contrib work for the community with desktop centric apps). Furthermore, unlike previous SuSE OS versions, the /usr/local is a fully (or pretty damn near) mirror of the root directory insofar as it has all the major subsets therein. My concerns is, unlike a generically empty /usr/local dir/subdir, the new config is much more complicated (or let's say "busy"). It was one thing to install something that had kludged libs or whatnot in the older version of /usr/local/lib because it stood out like a sore thumb. I mean it was with the only thing in there (at least at first) or it was easily differentiated from other program libs et al. Case in point: Old style /usr/local/lib********************************** srwxr-xr-x 7 root root 2808 2003-03-18 09:49 . drwxr-xr-x 27 root root 656 2003-05-10 06:07 .. New style /usr/local/lib********************************* YaST libe2p.so.2.3 libpamc.so.0 cpp libext2fs.so.2 libpamc.so.0.77 ld-2.3.2.so libext2fs.so.2.4 libpcprofile.so ld-linux.so.2 libgcc_s.so.1 libpthread.so.0 libBrokenLocale.so.1 libhandle.so.1 libreadline.so.4 libNoVersion.so.1 libhandle.so.1.0.1 libreadline.so.4.3 libSegFault.so libhistory.so.4 libresmgr.so libacl.a libhistory.so.4.3 libresmgr.so.0.1 libacl.la liblvm-10.so libresolv.so.2 libacl.so liblvm-10.so.1 librt.so.1 libacl.so.1 liblvm-10.so.1.0 libscpm.so libacl.so.1.1.0 libm.so.6 libscpm.so.0.9 libanl.so.1 libmemusage.so libss.so.2 libattr.a libncurses.so.5 libss.so.2.0 libattr.la libncurses.so.5.3 libthread_db.so.1 libattr.so libnsl.so.1 libtrash.so.1 libattr.so.1 libnss_compat.so.2 libtrash.so.1.5 libattr.so.1.1.0 libnss_dns.so.2 libutil.so.1 libc.so.6 libnss_files.so.2 libuuid.so.1 libcap.so libnss_hesiod.so.2 libuuid.so.1.2 libcap.so.1 libnss_nis.so.2 libxcrypt.so.1 libcap.so.1.92 libnss_nisplus.so.2 libxcrypt.so.1.1.1 libcom_err.so.2 libnss_winbind.so libz.so.1 libcom_err.so.2.0 libnss_winbind.so.2 libz.so.1.1.4 libcrypt.so.1 libpam.so.0 lsb libdb.so.2 libpam.so.0.77 modules libdl.so.2 libpam_misc.so.0 scpm libe2p.so.2 libpam_misc.so.0.77 security total 7065. Things could get buried very easily after a while, especially now. That's why the need for the rpm database. I can let the database keep track of this, so an rpm -e is much more preferable than looking at a tarball and trying to figure out what it installs and then finding it and removing it without removing shared files. Hmmm, what to do? Cheers, Curtis.
participants (3)
-
Curtis Rey
-
Matthew Johnson
-
Paul Conn