On St, 2002-02-13 at 11:25, Guillaume Rousse wrote:
> Ainsi parlait Michal 'hramrach' Suchanek :
> > I intended to create a fvwm-themes RPM. I looked into webalizer and
> > fvwm2 specs and I didnt beleive my eyes: the program is first unpacked
> > and built and then some of the resulting binaries are one by one
> > installed _manually_ from the spec.
> > Thats probably the reason why webasolve doesnt work (it should be named
> > webazolver) and fvwm-themes doesnt compile (it needs fvwm-config which
> > is not manually installed).
> > To automate the install process I'd suggest patched install which
> > installs into $RPM_BUILD_ROOT/dir instead of /dir (which should not
> > affect normal installs unless RPM_BUILD_ROOT is manually set)
> Have you ever created yourself a package ?
No, it seemed easier to compile tarballs until I got more than one Linux
installation :-)
> When there is no configure script with takes cares of this, or badly
> configured one, it's a lot easier to install manually than to either patch or
What is a proper configure script?
AFAIK most programs are configured and built with some prefix and are
non-relocatable. If you wanted to install them into different directory
you woluld need either patch the makefile to support RPM_BUILD_ROOT or
another variable of your choice or make the install utility which is
used by most makefiles support it.
> recreate a robust installer from scratch. Morevoer, there are sometimes part
> of the original program you don't want, such as gnome or kde specific
> shortcuts, etc...
Then, once installed into $RPM_BUILD_ROOT you choose which files you put
into which package. If you dont want some parts, you dont include them.
Or am I missing something?
> Anyway, feel free to send patches for making the two fornenamed package
> compliants, and even to forward them upstream to developpers.
> --
> Guillaume Rousse <[EMAIL PROTECTED]>
> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
>
>
--
Michal Suchanek
[EMAIL PROTECTED]
