rpms/flumotion/devel flumotion.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2

[Thomas Vander Stichele]

Hi Ralf,

> > Can you tell me what the exact difference will be here ?
> It's a matter of ownership.
> 
> %{_datadir} is a property of the package/rpm-spec you are currently
> building, it is by no means related/coupled to the directory being used
> by make-dummy-cert.
> 
> Try 
> rpmbuild --define '_datadir /tmp/foo'
> then you probably understand the difference.

I should have clarified - what is the difference in *practice* ? Any
spec can be made to break easily by doing stuff like this.
If you are saying that Flumotion's post script will break because
someone is installing an openssl rpm from some other distro that puts %
{_datadir} in /myowntree/share, then yes, you're right.  However, it
will break both ways.  I don't see what's the practical difference.

> It will tell rpmbuild to install files using %_datadir into /tmp/foo,
> but it will also bogusly tell the package to call 
> /tmp/foo/..../make-dummy-cert
> 
> => The package depends on
> /usr/share/ssl/certs/make-dummy-cert
> and does _not_ depend on
> %{_datadir}/ssl/certs/make-dummy-cert


So you're saying basically I can choose between:

Requires(post): %{_datadir}/ssl/certs/make-dummy-cert

%post
%{_datadir}/ssl/certs/make-dummy-cert

and

Requires(post): /usr/share/ssl/certs/make-dummy-cert

%post
/usr/share/ssl/certs/make-dummy-cert

?

If that's it, I agree, and I'll make it consistent in either of these
ways.

BTW, do you ever see anything else than openssl providing this file ?
Looking at the script I would be willing to bet you a fair amount of
money it won't :)

Thomas

Dave/Dina : future TV today ! - http://www.davedina.org/
<-*- thomas (dot) apestaart (dot) org -*->
Wouldn't want a heart that's been
dented by you
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.fm/