Ebuild Versioning Help - Upstream Changed Versioning Scheme

Message

Ian · Post by **Ian** » Sat Sep 12, 2015 8:48 pm

I'm trying to write a new ebuild to support an upcoming stable RC for the KiCad project. Unfortunately, the latest ebuild looks like this:

sci-electronics/kicad-20130518.ebuild

The KiCad developers have decided that the new stable release, the first in several years, will be called 4.0, resulting in an ebuild that should look like this:

sci-electronics/kicad-4.0.ebuild (or -rc1/2/etc)

20130518 is more than 4.0, meaning Portage thinks that the older KiCad ebuild is the newer one. How would I fix this? Does the old ebuild need to just be masked, and eventually removed from the tree?

Ian · Post by **Ian** » Sun Sep 13, 2015 12:09 am

Well, masking the older package seems to work, but isn't ideal. Is there any way to automatically include such a mask in an overlay?

Genone · Post by **Genone** » Mon Sep 14, 2015 10:37 am

I think profiles support a profiles/package.mask just like the regular tree. Not sure however how that works across repositories these days.

Ian · Post by **Ian** » Mon Sep 14, 2015 11:52 am

Tried that and it didn't seem to work.

Is it possible to just remove the older ebuild from the tree? Or would users (or developers?) still need to hard mask the older package to remove it, and install a new one?