[companion-discuss] Re: spec files for building 'Solaris CUPS Print Suite' ...
Laszlo (Laca) Peter
Laszlo.Peter at Sun.COM
Sat Jul 15 12:35:53 PDT 2006
On Thu, 2006-07-13 at 08:16 +0100, Paul Cunningham wrote:
> Using gcc was the way the freeware-gate (CCD) always did it. I think
> that was mainly because not all packages would build out-of-the box with
> Sun Studio so that made tracking updates easier and quicker.
> I just continued that, in my spec files, because the 'Sun Studio' I have
> access to is rather out of date (and fixing compile problems is not that
> interesting :-) ).
Okay, understood. I'll try to build them with Studio 11. It's a lot
better in terms of gcc compatibility (and otherwise too!) than previous
releases so most code I've tried could be compiled with little or no
code tweaking.
> > %define _unpackaged_files_terminate_build 0
>
> I knew there had to be someway of doing it, but I couldn't work it out
> so I patched it .
>
> >
> > But it's not a good idea to do so. It's better to use rm and rmdir
> > commands in %install to delete the files and directories you don't
> > want to include in the packages.
>
> The reason I did it, is because when building CUPS pkgbuild says there
> is a load of stuff installed that hasn't been packaged even though it
> has been. I tracked that down to pkgbuild not coping with non normalized
> paths (if I remember correctly). I raised a bug on pkgbuild for it.
> So yes I agree it's not a good idea but it was my work-around at the
> time. I should have said why I patched it in the README (I forgot, sorry).
Ah, okay. This is an open bug logged @sourceforge.net. Will be fixed
in the next release (as I keep saying...).
Thanks,
Laca
More information about the companion-discuss
mailing list