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

Remove all non-RPM content. #148

Closed
wants to merge 1 commit into from

Conversation

bowlofeggs
Copy link
Contributor

No description provided.

@elyezer
Copy link
Collaborator

elyezer commented May 5, 2016

I see that this is now added to the f23 branch. Can you explain a little bit what is the plan for it?

@bowlofeggs
Copy link
Contributor Author

On Thu, May 05, 2016 at 03:37:03PM -0700, Elyézer Rezende wrote:

I see that this is now added to the f23 branch. Can you explain a little bit what is the plan for it?

Sure! For one, my grand plan for this repository is actually to delete
it (muahahaha) as the majority of the code in here is not related to
packaging. Instead, I think we need two repositories: devel and
packaging.

devel: This repository will contain all the CI stuff, and also all the
Vagrant and other playpen stuff.

packaging: It's silly that this repository is called
pulp/pulp_packaging, especially given that it doesn't contain our
packaging. Since I'm doing new work, it makes sense to just create a
packaging repository. In fact, I may just delete this PR and do that
now.

The new work I am doing is to get our packaging out of the pulp
repository and into a packaging repository. There will be a branch for
each distro that we support (like f23). If we do this and create that
devel repository, the pulp repository should finally be free of all
non-upstream code and silly tags.

Randy Barlow
irc: bowlofeggs

@bowlofeggs
Copy link
Contributor Author

I created a new repository to hold the f23 stuff, so I'm closing this. See https://github.com/pulp/packaging

@bowlofeggs bowlofeggs closed this May 6, 2016
@bowlofeggs bowlofeggs deleted the cleanup_non_rpm_content branch May 6, 2016 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants