[bugs] [OpenIndiana Distribution - Bug #1118] /dev-il illumos version will break illumos onu
illumos bugs
bugs at lists.illumos.org
Wed Jul 6 06:41:10 PDT 2011
Issue #1118 has been updated by Andrzej Szeszo.
I was only experimenting with things. I am not sure personally what would be the best approach to versioning. I kind of like flexibility lack of branch version numbers brings though.
Not having branch version number would make life easier for people building their own packages. Especially when using pkgdepend to resolve dependencies. Software would not need to re-republished with every release of the distribution. It is possible that in many cases the resulting packages will install fine even on Solaris 11!
Also, people working on a distribution could choose to not to rebuild/republish every single package when preparing new release. Existing packages could be used instead.
Making incorporations less restrictive is another area to explore. We could make them to be just empty stubs in the development branch of the distribution. We could potentially also remove reverse dependencies on the incorporations from the actual packages. It would make it easier for people to create their own 'backports' of never software without messing with incorporation packages.
To not to make it a one big mess we could have separate repositories for releases: pkg.o.o/release/1.0, pkg.o.o/release/2.0, etc. Separate repos would let us lock versions of available packages. Other benefits of separate repos include ability to archive old unsupported release repos and letting mirrors to mirror only ones that are current. Also no surprises when doing pkg image-update when release 2.0 comes out and you want to stay on version 1.0 and continue receiving security updates/bugfixes.
I don't think technically lack of branch version number will pose any problems. I have not checked the source but people working on pkg5 don't seem to use it all the time. Check the version numbers at the bottom of this message for example:
http://mail.opensolaris.org/pipermail/pkg-discuss/2011-June/027123.html
I am sure pkg5's solver can be modified to handle X-0.148 or X-0.151 to X version transition in a special way. And also I'm sure dropping branch version number from illumos-gate could be coordinated with illumos devs so they don't have to worry about it ever again. It would actually be possible to make illumos generate differently versioned packages in one go and publish then to the same repo without taking too much extra space. Is there a reason you'd like to keep -0.148 branch version specifically for illumos delivered bits by the way (other than letting current pkg5/onu to continue to work on new OI)?
Again, I am not sure this is the way to go forward and I am probably forgetting about something. Idea itself though makes a lot of sense to me at the moment.
----------------------------------------
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
More information about the bugs
mailing list