On 05/15/12 07:46, Alan Coopersmith wrote:
On 05/15/12 12:43 AM, Steve Christensen wrote:
Greetings,
I have been looking at the IPS docs and perhaps I have missed the appropriate
discussions, but I have a number of items I would like to get clarified. If
all I need to have is a pointer to the correct documentation, please direct me
to the right stuff. I will start with two issues.
1. Suppose I want to have packages that are x86 or SPARC only. How do I put
the information into the package to make sure that someone wanting a SPARC
install does not get an x86 one? So, for example, if I have a package for
software foo-1.0 in SPARC and one in x86, do they have to be named differently
or put on two separate servers? What are the rules? I do not want users to
have to download a package that contains both.
If you're running an ipkg depot server, they will only download the bits they
need. They'd only get both bits if you're distributing the packages as full
*.p5m archives. If you do insist on per-arch packages, then yes, I believe
you'll need to either serve them from different publishers or give them
different names, and then learn to deal with user complaints that you make weird
packages, unlike every other package publisher in the world.
No, actually. You can publish each variant with the same package name
and even the same version (excluding timestamp). As long as you tag the
packages correctly, the solver will select the correct one.
However, that is *not* recommended as it can lead to confusion for your
users and will make your packages harder to manage.
It is strongly recommended that the packages be merged after publication
using pkgmerge.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
