Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Split pmbootstrap and aports in two repositories #383
There are different release cycles, that make sense for
A great benefit, that @MartijnBraam pointed out:
I'd be interested to start working on this packaging task. Would love to hear your thoughts on how we should handle this. Specifically the biggest pain point is the assumption that
In this future split, where would be the right place to have
Note that currently in the
Tough question and I'm almost out of postmarketOS time for today :/
I would like pmbootstrap to assist the user in getting the
The work path seems to be suitable for aports, so we would need to ask for that first.
Here's a rough draft from a user's point of view.
referenced this issue
Apr 15, 2018
How about a very simple workflow: if the aports directory is missing, we just show the
This looks like a very small change which I could do myself, we'd just need to decide the default path for aports.
This issue actually breaks my packaging for AUR (Arch Linux) :)
referenced a pull request that will
Apr 30, 2018
Thanks for working on this @marmistrz! Since moving the
I'm not sure if that covers everything, but that would be a good start from where we could do the first tests and fix whatever else comes up. So all this is quite some work, and while it would be nice if you could look into this, I don't think we should make such a big change in