Quoting Damien Carbery <damien.carbery at sun.com>:
> > %files
> > %defattr(-, root, bin)
> > %doc README ChangeLog CREDITS COPYING INSTALL NEWS
> > AUTHORS TODO ABOUT-NLS
> > %dir %attr (0755, root, bin) %{_bindir}
> > %dir %attr (0755, root, bin) %{_libdir}
> > %{_libdir}/*
> >
> > this is correct for me, even if i don't understand
> > why i need to specify
> > %_bindir because this directory is left empty by Tix
> > and if a guy (me for example) do a mistake in %attr,
> > many problems again...
> >
> You should not need the %_bindir line. The %doc line is not used on Solaris
> so it can be removed. Otherwise your %files section is perfect.
>
if i remove the line %bindir:
pkgbuild: ## Packaging complete.
pkgbuild: Transferring <SFEtix> package instance
pkgbuild: error: Installed (but unpackaged) file(s) found:
pkgbuild: /usr/bin
pkgbuild: pkgbuild: SFEtix.spec(54): Installed (but unpackaged) file(s) found
> > Another question if possible:
> > if you want to change the args of configure script
> > (for example to take
> > a new lib into account or to change cc to gcc?) you
> > have to write a
> > different spec file for each differents args?
> I'm not 100% clear what you mean. We always try to build on cc, only
> reverting to gcc if we absolutely have to.
> We do not have multiple versions of spec files, but we keep modifying the one
> spec file to enhance it.
>
for example, the package fltk, i need it with opengl and i'm not sure if the
spec file takes it into account, so i need to replace:
./configure
by
./configure --enable-gl
so in this case, do i have to create a new spec file or just change the existing
one?
--
gerard
