Skip to content
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

Closed
wants to merge 4 commits into from
Closed

qca gpg plugin fake use flag #27

wants to merge 4 commits into from

Conversation

damex
Copy link

@damex damex commented Feb 20, 2015

No description provided.

@kensington
Copy link

@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"
Copy link
Member

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

@johu
Copy link

johu commented Feb 20, 2015

EAPI3 is deprecated. Please move to newest.

@mgorny
Copy link
Member

mgorny commented Feb 20, 2015

@Pesa, to expand on this more.

|| ( qca[gpg] qca-gnupg )

causes Portage to consider qca-gnupg even when new enough qca[-gpg] is installed which results in awful blockers. This, combined with plain qca[gpg] deps would mean that every version of qca is installed fine without blockers. Users of old versions will be asked to set the flag early but they would eventually have to anyway.

@mgorny
Copy link
Member

mgorny commented Feb 20, 2015

@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.

@johu
Copy link

johu commented Feb 20, 2015

@mgorny why not stabilize newer version instead?

@Pesa
Copy link

Pesa commented Feb 21, 2015

I don't have any particular comment... TBH I don't really care about qca since I stopped using net-im/psi years ago.

Just a clarification:

Users of old versions will be asked to set the flag early but they would eventually have to anyway.

They will be asked because of what? qca consumers?

@mgorny
Copy link
Member

mgorny commented Feb 21, 2015

@johu, could be done. Though it would expose stable users to the issue for some time. Doing this on old version has the advantage that both branches of || () would be fine and blocker-free.

@Pesa, yes, if something depended on qca[gpg] or like, Portage will ask to add qca gpg to package.use.

@mgorny
Copy link
Member

mgorny commented Feb 21, 2015

+*qca-2.0.3-r1 (21 Feb 2015)
+
+  21 Feb 2015; Michał Górny <mgorny@gentoo.org> +qca-2.0.3-r1.ebuild:
+  Add USE flags for plugins that were integrated in the newer qca version. The
+  USE flags pull the plugins implicitly making it easier to create useful deps
+  on qca with plugins. Patch prepared by Roman Kuzmitsky (damex).

Along with some fancy arch profile masks for non-keyworded plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants