Ticket #168 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

[DISCUSS] keyword policy

Reported by: alonbl Owned by:
Priority: major Milestone: milestone4
Component: target Keywords:
Cc:

Description

Hello, As it looks like, current policy of keywords is as follows:

1. Place each package in separate file.

2. Place a keywords on a specific version and revision.

I suggest the following:

1. Group packages in a singe file.

2. For out of overlay packages, and if no good reason, choose only stable or none stable.

I also added portage-flags-common as there are some cases (like evas) that the same version should exists on host and target. Adding a "parent" node in both configurations.

Attached is my suggestion, not complete, but is the base.

If it is OK, I will commit.

Thanks!

Attachments

flags.diff (19.3 kB) - added by alonbl 3 years ago.
flags.diff

Change History

Changed 3 years ago by alonbl

flags.diff

Changed 3 years ago by sleipnir

I don't like the idea of keywording multiple packages in a file, as by now you easily see what packages are keyworded and in which version. In you scenario, one needs to first find the correct file (via grep or such) and then edit. We should rather discuss with armin76 about marking some of the packages we have as upstream stable.

About the common flagging: It's ok for me, but please keep one package per file.

Changed 3 years ago by alonbl

But it is much more difficult to know the REASON why this package is at ~arch.

Also you must grep in order to know the version anyway... :)

What do you think of removing the ~arch version for packages not in the overlay? Let's Gentoo maintainer decide what is stable and what is not.

Thanks!!!!

Changed 3 years ago by sleipnir

  • milestone changed from unsorted to milestone4

I started to clean up the versions that are stable in portage. However, the packges keyworded there all have a reason. Basically, I try first to install the current stable portage version, if this fails I try to install the latest portage version. In case this package compiles I keyword the file. If it also fails I try to fix the latest version in the overlay and keyword the file. The waterfall is the following:

  1. Try installing stable portage version. -> success: do nothing
  2. Try to install latest portage version. -> success: keyword latest package
  3. Try to fix the latest portage version. -> success: keyword overlay package

Hope this makes the process more clear!?

Changed 2 years ago by sleipnir

  • status changed from new to closed
  • resolution set to fixed

Ok the process is documented here, will close this ticket now.

Note: See TracTickets for help on using tickets.