Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Remove explicit provides #280

Merged
merged 2 commits into from
Aug 20, 2015
Merged

Remove explicit provides #280

merged 2 commits into from
Aug 20, 2015

Conversation

jordimassaguerpla
Copy link
Member

We are not using the provides for tracking the bundled gems, so we better don't have it because it creates noise.

I did it on a way that if we decide to get it back, we can revert the latest commit and we will have what we will probably need, that is "Provides: bundled(rubygem-foo) = XXX"

using bundled(...) will prevent any conflict with a packaging providing
embedded-.....
We set that for tracking which gems were bundled. However we are not
using that at the moment. Thus, let's remove it.

If we later decide to use it, all we need is to revert this commit.
@flavio
Copy link
Member

flavio commented Aug 20, 2015

Why aren't we using it? Don't we rely on that to have security mails for the gems required by the portus rpm?

@jordimassaguerpla
Copy link
Member Author

We don't rely on that. It was a proposal.

flavio added a commit that referenced this pull request Aug 20, 2015
@flavio flavio merged commit 752044e into SUSE:master Aug 20, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants