[OpenIndiana-discuss] Hipster upgrade problem

[Andreas Wacknitz]

Hipster is going where its maintainers want it to go.
If you want something else you need to invest. OI dev is stalled because
nobody (?) is working on it. So Hipster seems to be the only thing as long
as nobody works on an alternative.





Am 15.11.15 um 14:57 schrieb Udo Grabowski (IMK):
> So this post convinced me finally that /hipster is
> going nowhere.
>
> On 15/11/2015 07:31, Nikola M wrote:
>> On 11/14/15 03:44 PM, Stefan Müller-Wilken wrote:
>>> Hi Nikola,
>>>
>>> so that means that it is currently luck if the upgrade will work and
>>> in this particular case there's no way to force the upgrade to Perl
>>> 5.22? Too bad. :-(
>> Unless Hipster is freezed at some point that is marked upgradable and
>> tested, there is no point in time in hipster one can always upgrade to.
>> It doesn't mean it can't be made available soon, and you can help in
>> testing with it. I just suggested that zfs send of fresh install on
>> existing rpool is actually the fresh install you can get newer packages
>> into.
>>
>> Hipster does not have 'entire' one update to in the point in time where
>> update is tested now and hipster does not have  ability to bring back
>> older packages that used to work.
>> Bare in mind I was able to update from 151a8 to hipster, more then 2
>> years ago
>> but no one find important to freeze that state is some release to enable
>> update from /dev all the time since then.
>>
>> Hipster also does not have it's own source code repositories, but
>> download and patch sources from external sites - that is also not
>> something what distribution release is about, but would need it's own
>> source repositories available for distribution together with bineries
>> distribution, to continue from /dev.
>>
>> Hipster has rolling release model, meaning goal is not set for releasing
>> anything, there are only ISOs as snapshots from time to time.
>> Hipster is not controlling illumos that is shipped with it, nor applies
>> it's own patches, but compile and publish newest illumos after it is
>> available - that is great for testing and catching problems as they
>> arrive but is not for production.
>> If you want real continuation from /dev to something newer and tested,
>> one needs to contribute with ideas, testing, bug reports, package
>> maintaining and development.
>>
>> Alp and few people contributing and testing can't do everything alone,
>> all problems described have cure in establishing actual release and
>> support model
>> and that needs more people included, including you.
>>
>>
>
>
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss