Le lundi 3 juillet 2006 18:46, Kamran Karimi a écrit :
> Hi Geoffroy,
>
> > > your spec file is written to use the local system to create the
> > > package.
> >
> >You
> >
> > >should not do that, the following spec file is a good example of what
> > > you are supposed to do: at the URL
> > > https://oscar.openclustergroup.org/websvn, see the file
> > > OSCAR/pkgsrc/rapt/trunk/rapt.spec
>
> I added the line BuildRoot: %{_tmppath} to the .spec file. Then I changed
> the instal script so that the file will be created in $RPM_BUILD_ROOT/. Is
> this a move in the right direction? If so, then should I make sure that the
> needed directories (such as /etc, /bin/, etc.) are already created?
You go in the go direction. :-) The standard way to "install" files when
creating an RPM package is:
%install
rm -rf ${RPM_BUILD_ROOT}
install -d 755 ${RPM_BUILD_ROOT}/my/dir
install -d 755 ${RPM_BUILD_ROOT}/my/dir2
install -m 644 detectord.py ${RPM_BUILD_ROOT}/my/dir/my/file1
install -m 644 client.py ${RPM_BUILD_ROOT}/my/dir/my/file2
>
> After adding this line the entries in my %files section that use absolute
> paths (as in /usr/sbin/) break. In the example .spec file you sent me I
> noticed {_bindir} and {_mandir} variables. Are there variables to point to
> sbin and etc directories too?
I dunno these are not my packages, it was just an example (and i am not an RPM
expert, i use most of the time Debian which has a completely different binary
format). If you do not want to deal with these variables you can use the
absolute path directly.
--
Geoff
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
