Hi, Firstly, I think we all realize the herculean effort being made by relatively few people to maintain the current repositories and we're thankful for that. I'm completely certain that Jonathan and Filip and others, if they exist, are doing their best to manage it all. You guys are also great about helping out in IRC and updating packages when specifically requested.
>From my perspective as a customer: 1) Re-provisioning is a huge hassle and the QA involved makes the effort to upgrade this way near unbearable. We have to QA entire systems instead of a single software upgrade. This is not a good option. Also, never tell a customer that making something harder for them is a good thing. 2) Updates need to be available as they come out, especially security updates. 3) Release notes make little to no mention of non-pkgsrc related changes between datasets so what's going on there? Why the inter-dependency? Just have one repo for all of the datasets. 4) Regarding LTS, if it isn't LTS, don't bother releasing it. 5) One of the biggest cons of using SmartOS is the lack of software support. Joyent should invest heavily here to bring pkgsrc up to par with other *NIXes Thanks, Yonah On Fri, Jun 27, 2014 at 1:13 AM, Jonathan Perkin via smartos-discuss < [email protected]> wrote: > * On 2014-06-26 at 22:48 BST, Anil Jangity wrote: > > > Honestly, I am not sure I have the time and my clients aren't > > willing to analyze each of these reports to figure out which is > > important or not. > > That's fine, we just offer the choice. If you install many other > operating systems you don't get any notification whatsoever, so you > could just turn it off and pretend to be on Ubuntu etc :) > > > Is it possible to install+bootstrap these pkgsrc packages into a > > directory other than /opt/pkg? (will things break, e.g. SMF > > manifests) One way I think might help with upgrades if I can run > > multiple pkgsrc in a single zone? > > > > Something like: > > /data/2014Q1 > > /data/2014Q2 > > /opt/pkg -> /data/2014Q1 > > > > Perhaps then we could migrate from one set to another easily > > otherwise having to re-provision means that kind of requires a ton > > of other steps. > > No, this isn't possible, the binaries are built for a specific prefix, > in our case /opt/local. What you can do however is build packages > yourself into a custom prefix, there are some docs here: > > http://pkgsrc.joyent.com/bulk.html > > I plan to write a smaller one at some point which covers just > bootstrap + builds to make things simpler. > > It's unlikely however that this would be any simpler than just > re-provisioning, and again you would miss out on any of the non-pkgsrc > upgrades introduced in newer images. It's more for the cases where > you want to build packages with non-standard options, etc. > > -- > Jonathan Perkin - Joyent, Inc. - www.joyent.com > > > ------------------------------------------- > smartos-discuss > Archives: https://www.listbox.com/member/archive/184463/=now > RSS Feed: > https://www.listbox.com/member/archive/rss/184463/23550547-46dd9120 > Modify Your Subscription: > https://www.listbox.com/member/?&; > Powered by Listbox: http://www.listbox.com > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
