[bugs] [OpenIndiana Distribution - Bug #1118] /dev-il illumos version will break illumos onu

[illumos bugs]

Issue #1118 has been updated by Rich Lowe.


I can't speak as to what OI want to do, but it's very likely that incorporations _don't_ give you the behaviour you wish for in this case.  Incorporation at the timestamp level is likely possible, but it would make generating the incorporation rather difficult, and we _do_ have cases where lock-step upgrade of packages not only appropriate, but necessary (system/library and system/kernel, for eg).  This also makes "package FOO didn't upgrade" a completely silent failure, and gets us back to people running random untested gloms of software.  I would think about it carefully before going that route.

More technically, I don't know whether a missing branch version is:
# Meant to be allowed (I thought it wasn't)
# Greater or less than a specified one (so it may still screw illumos)

I'm still in favour of giving illumos a large branch version, however, if you're willing to _remove_ branch versions from your OI packages, surely you'd be similarly willing to leave illumos at 0.148 where we put it?  The end results are identical as far as install and upgrade are concerned.  This also, conveniently, wouldn't screw us (but would mean /dev-il users had nowhere to go)
----------------------------------------
Bug #1118: /dev-il illumos version will break illumos onu
https://www.illumos.org/issues/1118

Author: Rich Lowe
Status: New
Priority: High
Assignee: 
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: 


In the /dev-il repo the build version of illumos was incremented to 0.151, to match everything else.   Because in the illumos source tree the packages remain at 0.148, this means that any packages built from our source tree will no longer install on OI.  It'd be nice to avoid that.

The problem is that if you keep our current version number, people running oi_148 will get the upgrade, because the incorporations aren't (and perhaps can't be) tight enough to prevent it.

Solutions I can think of are:

# Leave illumos version at 0.148, trust that we have done nothing incompatible, and that we'll bump that number if we do
# Have illumos bump their version to match yours, and continue to do so (I'm against this)
# Have illumos bump their version _far_ past you, and give you your own space to play in, as long as you never catch back up and screw it again (ie, call illumos 1.0, and leave you guys with 0.* in which to play).  This is probably the smoothest solution, but I'm sure people will argue about the merits of calling something "1.0", even in a place nobody really looks.




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account