great idea for updating packages on SuSE?
For the last few days I have been trying to get a jabberd server working with MSN transport. It didn't work but some help info I read suggested that there were problems with Curl older than a certain version. I saw that SuSE 9 was older so I tried to update. I didn't see any updates on the SuSE site so I went to the source and downloaded. Since there were very little instructions provided, I built with the standard ./configure make make install The problem is that I didn't know where it got installed and when I ran curl-config --version I saw it was the old one. With a little research I found where it was installed and were was the SuSE version. Finally on the curl website I found more info and was able to ./configure correctly. While doing this last night an idea came to me. SuSE has many packages and some are not installed in the default locations that you would get if you just used ./configure. Why not provide a database of the packages and the build/install options such as ./configure --prefix=/SuSE/path/to/install? Wouldn't this make it so much easier to find were packages are and make it easier to upgrade them? It could either be on the SuSE web site or perhaps even within YaST? What is your opinion? Is this something I could submit to SuSE feedback or is it silly? Damon Register
Why not provide a database of the packages and the build/install options such as ./configure --prefix=/SuSE/path/to/install? Wouldn't this make it so much easier to find were packages are and make it easier to upgrade them? It could either be on the SuSE web site or perhaps even within YaST?
This information is available in the .spec file for each package. It's worth noting that no package uses the ./configure defaults, because ./configure invariably defaults to --prefix=/usr/local -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 9.0) GNOME updates for SuSE: http://www.usr-local-bin.org
James Ogley wrote:
Why not provide a database of the packages and the build/install options such as ./configure --prefix=/SuSE/path/to/install? Wouldn't this make it so
This information is available in the .spec file for each package. Now may I ask a possibly silly question? Where is this .spec file? If I am don't know where is the location of some installed SuSE package, how would I know where is the .spec file?
./configure invariably defaults to --prefix=/usr/local so I am learning. One package I updated recently even required a separate prefix setting for the include and lib directory in order to be where SuSE had that package
Damon Register
Now may I ask a possibly silly question? Where is this .spec file? If I am don't know where is the location of some installed SuSE package, how would I know where is the .spec file?
The .spec file is in the src.rpm - the source package -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 9.0) GNOME updates for SuSE: http://www.usr-local-bin.org
participants (2)
-
Damon Register
-
James Ogley