Hi Rein,
On Tue, 2008-08-19 at 19:22 +0300, Rein Remmel wrote:
> I'm interested in using pkgbuild in one of our projects. It's nice to
> see that your trying to add IPS support. Great work so far:) Major
> blocker for me at the moment is inability to mark configuration files so
> that they won't get overwritten at next update.
I've applied that part of your patch in the ips2 branch, thanks.
> When I tried to improve it I found that IPS manifests point to files in
> SRV4 package. This makes it impossible to build IPS only packages. It'll
> probably break if you create srv4 package in other format than
> filesystem.
Yes, I have already realised that but there is a good reason for
doing it this way. If the paths in the manifest point to the
buildroot, the manifest becomes useless after the build because
the buildroot gets deleted. If the manifest points to the
files in the SVr4 package, you can publish a package in a
separate step (possibly to multiple IPS repos) so it gives
you more flexibility.
We need to do something about datastream. One option is
keeping both the datastream and the file system format
packages. This is a waste of disk space but on build systems
the packages are usually tiny compared to the built source
tree, so it shouldn't be a huge overhead.
> To illustrate what I need I have included a patch (applied to beta from
> http://blogs.gnome.org/gman/2008/08/12/playing-with-ips-and-sfe-part-ii/ )
>
> Since scripts are not supported in IPS, it would be good to support
> actions like user, group, legacy, driver, service..
Yes.
> Any idea, how to implement them?
I haven't looked into it in any detail yet, but we will probably
need new macros in the %files list. For example %action(user ....)
> There should be some standard, since
> the number of actions is growing and each of them also have attributes:s
> How will that affect RPM compatibility?
It'll break RPM compatiblity unfortunately. But if you want to
use the same spec files on Linux and Solaris you have other options,
for example in the JDS project we use Solaris spec files that
refer to sections of the Linux spec file:
%use foo = foo.spec
...
%prep
%foo.prep
Where foo.spec is the RPM spec file.
> Someone mentioned, that IPS support is developed in ips2 branch. Is this
> public?
Sure.
You should be able to check it our from CVS anonymously:
cvs -d :pserver:anonymous@pk...:/cvsroot/pkgbuild login
cvs -z3 -d :pserver:anonymous@pk...:/cvsroot/pkgbuild co -r ips2
pkgbuild
Laca
|
