> 
> On 03/10/11 01:38 AM, Robert Milkowski wrote:
> > I think it should as otherwise creating packages in Solaris is rather
> cumbersome unless I missed some tools which well might be the case.
> 
> I'm not sufficiently versed to answer your other questions, but I'm surprised
> you think creating packages is so cumbersome.
> 
> There a lot of simple  applications that can be packaged very simply with
> something like:
> 
> configure
> make install DESTDIR=/tmp/build/
> $(pkgsend open [email protected])
> pkgsend import /tmp/build
> pkgsend close
> 
> If anything, I think packaging with IPS tends to be simpler because it doesn't
> conflate a build system with packaging, so you're free to build the software
> however you like, and can then package the result regardless of how you
> built it.
> 
> If you have specific concerns or questions surrounding the publication
> process, feel free to comment.

Until you need to express dependencies, file permissions, actions, meta 
information (packager, etc...)...
It is so much easier to start with a .spec template, list all your files, etc. 
and then ask a tool to generate whatever is needed so it ends up in a 
repository.
Notice that with .spec files you don't have to include the method to build a 
software, you could put only sections which describe what and how you want to 
package.
With what you shown above the problem is that one needs to come up with the 
tooling on its own.
Main problem right now I think is lack of step-by-step procedures, 
documentation and some easy to re-use templates. On top of that all is new and 
it takes some time to find information. 
For example I just quickly read thru pkgsend(1) and pkg(1) - both mention 
manifest but I can't find a man page describing the manifest syntax... How do I 
add a smf manifest and make sure it gets imported? I could (and I will have to 
I guess) look at other manifests and reverse-engineer it which is not that 
complicated but takes some time.

Although pkgtool/pkgbuild seems to be very good here as it allows to use .spec 
files *very* similar to rpm spec files lot of people are already familiar with.


So in summary the main issue right now is that pkg is new, there is lack of 
documentation, examples and man pages. Although I've probably missed many of 
them.


Ps. pkgsend import - neat, but it is not clear from the man page how it handles 
symlinks, how can I specify different file permissions/owners that’s what on 
filesystems, etc.



_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to