Hello list, I am wondering, does anyone know: 1.) If there is such a thing? 2.) What it would be? As to how SuSE installs packages from the source for the './configure' script? What I mean is: is there a standard set of rules that they use when running the configure script to install all the pieces of software in the various locations on the file-system? <example> When installing the latest version of apache, the configure script is setup for '/usr/local/' then it creates the directory of the package it's going to install - 'apache'... (this causes all kinds of problems with the SuSE init-scripts) --But when you install SuSE's RPM of Apache, it has all the binaries in '/usr/sbin/' and the 'conf' file is in '/etc/httpd'... (this one works, because the init-script is setup, but this package might not have everything you want) </example> I'm just wanting to know if there is an easier way to "comply" with the standard system layout SuSE has implemented. Hope this explains what I'm looking for. TIA, ---=---=---=---=---=---=---=---=---=---=--- .~. .~. /V\ /V\ // \\ // \\ /( )\ /( )\ ^^-^^ ^^-^^ Travis Owens towens@linuxmds.com
On 15 Mar 2002 11:34:32 -0600
Travis Owens
I am wondering, does anyone know:
1.) If there is such a thing? 2.) What it would be?
As to how SuSE installs packages from the source for the './configure' script?
What I mean is: is there a standard set of rules that they use when running the configure script to install all the pieces of software in the various locations on the file-system?
<example> When installing the latest version of apache, the configure script is setup for '/usr/local/' then it creates the directory of the package it's going to install - 'apache'... (this causes all kinds of problems with the SuSE init-scripts)
--But when you install SuSE's RPM of Apache, it has all the binaries in '/usr/sbin/' and the 'conf' file is in '/etc/httpd'... (this one works, because the init-script is setup, but this package might not have everything you want) </example>
If you want to comply with suse's method, you probably should use their "source rpms" for each package. It comes with the configuration files usually set. However, their is nothing from stopping you from installing the source from apache in their default directories. You can have 2 different versions of apache running. You just have to read the docs and remember which config file goes with which httpd daemon. This is true of almost all packages. -- $|=1;while(1){print pack("h*",'75861647f302d4560275f6272797f3');sleep(1); for(1..16){for(8,32,8,7){print chr($_);}select(undef,undef,undef,.05);}}
On Fri, 2002-03-15 at 12:23, zentara wrote:
If you want to comply with suse's method, you probably should use their "source rpms" for each package. It comes with the configuration files usually set.
Yeah, I know, but obviously, they're not going to have _every_ package out there. They're definitely not going to have the latest and greatest package versions in most cases, nor will the SuSE RPMs be compiled with all the features you may want. Hence -- the installation from source!
However, their is nothing from stopping you from installing the source from apache in their default directories. You can have 2 different versions of apache running. You just have to read the docs and remember which config file goes with which httpd daemon.
I know I can install in the default directories, but I'd rather install where I don't have to make 16K adjustments to the init-scripts or whatever to make the system work. When I installed qmail I was able to install via a tutorial, and it was a very well-thought-out tutorial. It had you create the install directory your self as well as several directories inside it, the catch being, these internal directories were actually symlinks from other places on the machine. (i.e. /var/qmail/control actually = /etc/qmail -- this way you can edit any of the configs from /etc/) :) Pretty clever idea! If any distro would do that with the packages, it would serve to explain a layout for future package installs much easier. (i.e. install package xxx in /usr/local/xxx then link the relative info to /usr/bin /usr/man /etc/xxx and so on) My 2 cents on File System structure. T.
On Friday 15 March 2002 21:23, Travis Owens wrote:
If any distro would do that with the packages, it would serve to explain a layout for future package installs much easier. (i.e. install package xxx in /usr/local/xxx then link the relative info to /usr/bin /usr/man /etc/xxx and so on)
My 2 cents on File System structure.
And this is where the Linux filesystem standard steps in... not yet, but going in the right direction :) Gr.. Hertog
On Fri, Mar 15, 2002 at 11:34:32AM -0600, Travis Owens wrote:
Hello list,
I am wondering, does anyone know:
1.) If there is such a thing? 2.) What it would be?
As to how SuSE installs packages from the source for the './configure' script?
What I mean is: is there a standard set of rules that they use when running the configure script to install all the pieces of software in the various locations on the file-system?
standard system layout SuSE has implemented.
Hope this explains what I'm looking for.
I think you are looking for this: http://www.suse.com/~grimmer/Package-Conventions/ -Kastus
participants (4)
-
Gert-Jan Rodenburg
-
Konstantin (Kastus) Shchuka
-
Travis Owens
-
zentara