Thanks for informations. But I think that could be fine an enhancement of hop features for permit manage of different branches for different repositories.
In production could be helpful have repositories with customized packages that could be released on different revisions. For example. Repository myrepo1 at branch 1.0 contains mypackage-1.0 , at branch 2.0 contains mypackage-2.0 (dev) For production environment is used branch 1.0 until mypackage-2.0 is stable. And could be released bug fix release mypackage-1.x for example security issue , etc. always on branch 1.0 I prefer do not use package.mask for this. My cent. On Fri, 2015-05-08 at 12:17 -0500, Wolfden wrote: > afaik the hop is depreciated as we moved to a rolling release many > years ago. For example when sabayon was 3.0 to get to 4.0 one would > of used the hop command to get to the 4.0 repo to upgrade to 4.0, but > there is no need for that now since we are rolling now. > > On Fri, May 8, 2015 at 7:33 AM, Ge@@ru <[email protected]> wrote: > > Hi guys, > > > > I have a quetion about "hop" feature, that I think could be used to > > permit management of different revisions on repository server. > > Is this correct ? > > > > Why execution of hop command change branch on all repositories > > configured and not only with a particular repository ? Why doesn't > > permit configuration of diffent branch in different repositories ? > > > > For example permit both: > > > > sabayon.linux.org 5 > > > > repos2.org 1 > > > > on same os. > > > > Is there a particular motivation or not ? > > > > If not I will investigate to permit customization of hop feature > > for > > repository. > > > > Thanks in advance. > > > > I hope for a feedback. > > > > G. > > > > > > > > >
