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

pacsync $repo and pactrans #4

Closed
AladW opened this issue Feb 21, 2016 · 3 comments
Closed

pacsync $repo and pactrans #4

AladW opened this issue Feb 21, 2016 · 3 comments

Comments

@AladW
Copy link

AladW commented Feb 21, 2016

pacsync allows syncing a specific repo, while pactrans only allows a general --sysupgrade for all repos. Would it be reasonable to implement a per-repo --sysupgrade for pactrans?

Example use case: Updating packages from a local (file:///) repository.

@andrewgregory
Copy link
Owner

The ability to sync individual repos follows very naturally from the nature of the tool and the way libalpm handles repo updates. The same cannot be said for repo-specific sysupgrades. That would require pactrans to skip registering unwanted repos or altering their usage from what is in pacman.conf. I am not inclined to add that level of granularity to pacutils, at least not at this time. It could, however, possibly be accomplished by using pacconf to build a temporary config file with only the desired repos. I would need to add an option to get the non-repo settings from pacconf but it would look something like: pactrans --sysupgrade --config=<(printf "[core]\n"; pacconf --repo=core)

@andrewgregory
Copy link
Owner

92eee4e adds the ability to get just the global options from pacconf, making it possible to generate a config file with just the desired repo with something like:

printf "[options]\n"
pacconf --options
printf "[%s]\n" "$repo"
pacconf --repo="$repo"

@AladW
Copy link
Author

AladW commented Sep 8, 2016

Thanks

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

No branches or pull requests

2 participants