Jump to content
  • 0

kit's master branches


skunk

Question

hello again,

i've the following set into my ego.conf:

xorg-kit = 1.19-prime
media-kit = 1.1-prime
kde-kit = master

however on today sync i've got this message:

"Kit kde-kit branch master specified in ego.conf is not currently active; using default kit instead."

so why can i not choose kde-kit's master branch anymore in ego.conf?

i've forced the master branch checkout by adding:

@git -C /home/meta-repo/kits/kde-kit checkout origin/master || true

into eix-sync.conf, however i wonder why these kind of hacks are necessary...

thank you

Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 1
  • Funtoo Linux BDFL

The reason is because we stopped updating master for kde-kit, and ego knows that it's not going to get any updates. We may add it back in the future after a server upgrade, but I needed to cut back on the time required to generate all the kits for now.

Link to post
Share on other sites
  • 0

ok, i can live with it for some time, however why forcing everybody on 5.10-prime branch if they where on master if neither branch won't get updates anymore?

downgrading from master to 5.10-prime isn't something worth doing if you already are on plasma-5.11.1/apps-17.08.2/framework-5.39, imho...

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...