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

Patch sys-apps/portage to point to galapagos repo #12

Closed
Elizafox opened this issue Dec 12, 2016 · 8 comments
Closed

Patch sys-apps/portage to point to galapagos repo #12

Elizafox opened this issue Dec 12, 2016 · 8 comments
Assignees

Comments

@Elizafox
Copy link
Member

This one is a pretty trivial task, if anyone feels up to it.

@CraigInches
Copy link
Member

Ill take a crack at it this evening

@Elizafox
Copy link
Member Author

Excellent. Just edit the repos.conf file installed by it and it should be good to go.

@CraigInches
Copy link
Member

As mentioned on IRC, I dont think a patch is necessary to the ebuild. But we need to look at creating our own stage 1,2,3 tarballs for installation, and for now leveraging the tar balls provided by Gentoo for the base install and then converting over.

@mjeveritt
Copy link
Member

I think that's closely related to #11 - probably worthy of a separate Issue tbh. Someone needs to get to grips with catalyst.... ;)

@CraigInches
Copy link
Member

Yeh, I was looking at catalyst and the stages last night. Its definitely worth another issue. Ill leave this open till Ive finished confirming that the edit to the tarball is all that is required to get us rolling with portage, and our own repo. Its just /usr/share/portage/repos.conf that needs replacing in it for that to happen.

@Elizafox
Copy link
Member Author

Elizafox commented Dec 14, 2016

There needs to be a patch in the ebuild to patch the default system repos.conf or it will default to gentoo's, clobbering any user configuration to the contrary.

@CraigInches
Copy link
Member

Patched and E builds updated

@mjeveritt
Copy link
Member

Not grouching here, honest (!) but has a second person run through craig's new process? I have faith, but always good to have a second/third/etc ACK :)
I think idella4 is having a stab, but might need some explaining and walking-through!

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

No branches or pull requests

3 participants