Laszlo (Laca) Peter writes: > On Mon, 2007-01-08 at 13:57 -0500, James Carlson wrote: > > The existing rule is that you need to build on a system that is at > > least as old as what you plan to support. You can then test for that > > minimum system version and (because libraries are carefully designed > > to be stable ;-}) run on any newer version. > > Exactly. But how do I express this as a package dependency? > In other words, what stops users from installing my package > on a system that is older than the oldest I plan to support?
If you avoid microscopic package versioning, you either tell customers "supported on Solaris X and above" and be done with it, or (if you're feeling pedantic) you test uname -r and the existence of the objects (such as /usr/lib/libfoo.so.1) in question during a preinstall script. For things on existing versions of Solaris, delivery of patches gives you a richer way to express dependency, because of just this problem. It's not well connected with packaging, though. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
