RPM Loader Script - V0.1

Adi Linden [email protected]
Thu, 3 Feb 2000 00:15:51 -0600 (CST)


Hi,

> Just thought I'd update you on my latest script.
> I wrote this today so I could build my fvwm2 package.
> So far...
> 
> pwl_rpmload EXE fvwm2
> 
> copies the RPM file from the RH disk, installs it
> and copies the files into:
> 
> Embedded_Build/sources/fvwm2
> 
> Files created here include:
> 
> fvwm2-3.0.5-15.i386.rpm
> -- the rpm copied from Red Hat (if the package is not installed)
> fvwm2-3.0.5-15.pkg_list
> -- list of files from the package (without man/doc/info files)
> fvwm2-3.0.5-15.pkg_dep_list
> -- not created yet, piped to the screen - list of dependencies reported
>    by rpm
> fvwm2.pkg_files
> -- directory containg the files to be tarred for the package.

The problem with using binary rpms is that they might require PAM and/or
ncurses...

> Note: the xxx.pkg.list file is not changed if it already exists.
> Thus, when you figure out which other files don't belong in the
> package, you can edit this file.  THIS FILE IS ALL YOU NEED if you
> have RH install disk!

Neat!

> To Do: find each of the dependent files on your system and copy them
> into the dependencies directory. (HOW DO YOU FIND FILES ?? Locate??)
> Package the dependencies as  xxx.libs or something and install that 
> as another package, i.e.

You do 'ldd binary_name' or 'ldd lib_name'. That will result in a bunch of
libs required for those libs and binaries to function. The 'file' command
will tell you if the libs or binaries are stripped. The stripping can be
done with 'objcopy' or 'strip'...

> To Do: load the source rpm, install it, copy the source files
> and compile everything.  Then copy the binaries from the SRC 
> directory into the pkg.files directory.....

Yup, that would be the best way of doing it. Or... download the original
sources and compile from scratch. Then make a build script and a patch
file... Otherwise it might get messy if we build some packages from rpm
and others from tar...

> To Do: 
> I need to integrate this script, with the "package" script (should we
> change this to pwl_package?? ) under the "Package Management" Main
> menu Item.

package just creates a package from the contents of Embedded_Build/mnt
doesn't it?

TTYL,
Adi

---------------------------------------------------
See the list archives at http://adis.on.ca/archives/
See the PWL homepage at  http://embedded.adis.on.ca
---------------------------------------------------