Well, I was not focused on security, but on updates safety issues, and, more in general, to find a way to deal with those willing to use Sabayon but without updates. They are a numerous minority (~30% of the users I follow).
2011/6/23 Cloud X. Strife <[email protected]>: > This is true, but not all stable releases are "secure". Security is one > reason for updates, but I do see where you are coming from. Updates break > things, its inevitable. And many users I set up aren't tech savvy. > > On Jun 23, 2011 10:53 AM, "Danilo Pianini" <[email protected]> wrote: >> Please consider, as option, the possibility to have a rolling branch >> along with fixed ones. Our default would be to be rolling, but with an >> equo hop you may switch to a fixed branch, like a snapshot of the >> status of our distro at a time. This would allow the user to install >> new software without being forced to do the world update. >> >> My proposal is not coming from the deep perversion of my brain, but is >> because many users DON'T like to update things, they are happy with >> the system as it comes, but they need some more software. >> I made a raw copy of the entropy repository on a small server and >> pointed their repositories.conf to this resource. It worked, they are >> really happy and they will make a new installation in three years or >> so (ASA they will mess up things by themselves). >> >> I wonder if we may want to generalize this support - in case, we would >> be the first (AFAIK) with both rolling and milestone based release >> systems. The way might be to rely on branching. >> >> It would require almost zero maintaining*, very limited bandwidth**, a >> lot of disk space***. >> * it's a raw copy, no further maintaining needed >> ** if you don't get updates, you just download packages when you >> install something new - which is definitely more rare >> *** each copy is around 80GB if I don't wrong, supposing we want to >> make a milestone for every release and offer "support" for five years, >> we'd need 1.2TB >> >> >> 2011/6/23 Fabio Erculiani <[email protected]>: >>> On Thu, Jun 23, 2011 at 4:14 PM, Danilo Pianini >>> <[email protected]> wrote: >>>> Like it, I agree. >>>> A question for you. In the current developing model, which is the >>>> meaning of "equo hop"? >>>> Will we have an hop for each release, not being rolling anymore or >>>> will it be just ignored? >>> >>> It depends. Perhaps a new GCC major version would require the whole >>> tree to be rebuilt. In this case, we'll trigger a branch fork, thus, >>> in this case "equo hop" is required. >>> >>>> In case branching is no longer used, I have a proposal to exploit this >>>> equo feature in an useful and - to the best of my knowledge - >>>> innovative way. >>>> >>>> >>>> >>>> >>>> -- >>>> Ing. Dott. Danilo Pianini >>>> Phone: +39 320 4136 573 >>>> Skype: dany.sk >>>> >>>> >>> >>> >>> >>> -- >>> Fabio Erculiani >>> >>> >> >> >> >> -- >> Ing. Dott. Danilo Pianini >> Phone: +39 320 4136 573 >> Skype: dany.sk >> > > > > -- Ing. Dott. Danilo Pianini Phone: +39 320 4136 573 Skype: dany.sk
