Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

Leaderboard

Popular Content

Showing content with the highest reputation on 12/02/2018 in all areas

  1. Hi All, Within 12 hours, I plan to move 1.3-release to BETA status. Along with this comes the very important change on 64-bit platforms -- I am removing multilib and making "pure64" compatibility the default. This means that 1.3-release builds with the x86-64bit arch will be 64-bit only. This is done for a variety of reasons, most important of which is that the world has had a 64-bit PC instruction set for approximately 15 years. It is time to drop 32-bit support. For those who still need 32-bit support, it will be available via a Funtoo 32-bit chroot setup. The story behind multilib is rather complex and interesting, and might be the focus of a future blog post, but for now, you will just have to trust me -- multilib support in Gentoo is a pain in the butt. It takes a lot of effort to work with and slows us down. Our efforts are best spent in other places, and chroot should work for the vast majority of users who truly are running a critical 32-bit application (other options are 32-bit containers, etc.) EDIT: Upgrade Instructions Here: https://www.funtoo.org/Upgrade_Instructions/1.3-release Best, Daniel
    2 points
  2. so you looked at github and explored git locally - no sign of ego kit list here. You wonder if there is a way to do it with ego or any funtoo specific command -> ego kit list 1.3-release will show once you switch to 1.3-release in ego.conf [global] release = 1.3 the stability tag: current - tracking gentoo prime - somehow seen as good for production anything else - alpha, beta, dev => not good for production if you are not a developer
    1 point
  3. I'm not losing my time anymore with you. As said, you didn't read or understood the genuine post. Also you just copied and pasted the command I proposed on the first post which obviously doesn't answer any of the questions set out. By moving to any kit git repo locally one can git ls-remote (or fetch all branches and check them out) and see what branches exists. But What I would like to know if there's any command to see how many or which branches exists for a given kit repo. Also I would like to query a description/definition for the stability associated to those branches. Unfortunately none of these can be achieved by ego, AFAIK. ego kit -v list|status doesn't show all the existing branches for a given kit repository. Neither describes it's stability. As example, you should be able to comprehend kde-kit has 3 git branches which are not shown by ego kit, nor a description for its stability: ego kit -v list /var/git/meta-repo (updated 5 hours 42 minutes ago): kit is active? branch stability kde-kit active 5.12-prime prime So my questions persists. Is there any way to get this kind of information through system utilities or one should dig into with git commands and then decide which branch suits best reading untrusted sources? Kind regards,
    0 points
×
×
  • Create New...