New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qca gpg plugin fake use flag #27
Conversation
@Pesa maybe you have some comments? The idea of the fake USE flags is to avoid blockers difficult for portage to resolve. |
|
||
LICENSE="LGPL-2" | ||
SLOT="2" | ||
KEYWORDS="alpha amd64 ~arm hppa ~ia64 ppc ppc64 sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have to drop stable keywords to unstable when bumping. Repoman doesn't allow you to commit straight to stable. This can be done e.g. using:
ekeyword ~all qca-2.0.3-r1.ebuild
EAPI3 is deprecated. Please move to newest. |
@Pesa, to expand on this more.
causes Portage to consider |
@johu, this is going almost straight to stable. Changing EAPI is not the best idea, and a waste of time consider the ebuild's eventually going to be removed. |
@mgorny why not stabilize newer version instead? |
I don't have any particular comment... TBH I don't really care about qca since I stopped using Just a clarification:
They will be asked because of what? qca consumers? |
Along with some fancy arch profile masks for non-keyworded plugins. |
No description provided.