On 4/16/2013 15:10, Jonathan Perkin wrote:
pkgin has no benefit to users who build from source, no. It is for users who wish to only use binary packages that they have built themselves or are provided by a third party.
Hmm, I'm sorry for derailing (temporarily) my own thread, but in the context that pkgin/nih was designed for, pure binary package mgmt, how well do they handle switching repos?
For example, say I have a system populated with 2012Q4 packages. If I point pkgin (for example) at a 2013Q1 repositority, will it seamlessly be able to graft in new packages from 2013Q1 even though dependency versions might be different?
Or are you pretty much resigned to desinstalling everything and reinstalling their counterparts from the new repository?