tir, 28.06.2005 kl. 17.55 skrev Bob Proulx:
> > I was curious as to how I am supposed to create symlinks that are for
> > this package, upon installation.
>
> Create them normally in the %install section. List them normally in
> the %files section.
>
> > When I list the links in %files and they go through the install routine,
> > what I end up with is copies of the files that should have been
> > symlink'd - not the symlinks themselves.
>
> That is not the behavior that I am seeing here. Can you show your
> spec file? I do this all of the time and it works for me.
Could you please comment? I'm open for everything at the moment ...
--Tonni
--
> > I am creating symlinks manually from within %post. This is the only
> > solution which I've found.
>
> You should not need to do that.
>
> > Are there any special precautions which I need to take when creating
> > symlinks, and creating them properly, so that they are removed when I
> > uninstall an RPM?
>
> The only problem I have seen is that a dangling symlink won't be
> expanded as a file glob. In that case it is best to list it
> explicitly. But I usually touch the target in the buildroot so that
> it no longer dangles at the time of glob expansion.
[...]
cd $RPM_BUILD_DIR/%{name}-%{version}/build_unix
install -m 644 db.h %{buildroot}/usr/local/BerkeleyDB.4.2/include
install -m 644 db_cxx.h %{buildroot}/usr/local/BerkeleyDB.4.2/include
install -m 755 .libs/libdb* %{buildroot}/usr/local/BerkeleyDB.4.2/lib
install -m 755 libdb.a %{buildroot}/usr/local/BerkeleyDB.4.2/lib
pushd %{buildroot}/usr/local/BerkeleyDB.4.2/lib/
ln -s libdb-4.2.so libdb.so
popd
%files
[...]
Thanks!
--Tonni
--
mail: tonye@xxxxxxxxxxxxxx
http://www.billy.demon.nl
