* On 2018-05-01 at 11:43 BST, Robert Fisher wrote: > I build pkgin (pkgsrc?) packages of certain tools, customized to my own > needs. To get them on my hosts I stick them in Manta, and config-management > downloads them and installs them from the local filesystem. This has always > seemed crude and clumsy, but works. > > Now I'm looking at deploying my own code via pkgin packages, but I can't > see an efficient way to do it. My stick-it-in-Manta approach can't cut it > with frequently rebuilt packages: I need a proper repo. If I used, say, > ubuntu, my CI pipeline would drop the package in Artifactory or Gemfury or > whatever, and it would be pulled down from there by the proper packaging > tools on the next config-management run. > > How would I (could I, even?) implement a similar approach with pkgin on > SmartOS? I haven't been able to find any documentation on running > additional private repos, which is starting to make me wonder if it's even > possible. > > Before I start re-inventing wheels, is there any accepted best-practice I > should begin with?
I wrote a brief guide to creating local packages a while back here: https://www.perkin.org.uk/posts/creating-local-smartos-packages.html That's for generating packages outside of a pkgsrc environment and making them available via HTTP. If you prefer to build them using pkgsrc, then you can create a separate pkgsrc tree under pkgsrc/whatever/pkgname and link to the pkgsrc infrastructure from there, as we do with e.g. pkgsrc-joyent: https://github.com/joyent/pkgsrc-joyent If I've missed anything out please let me know, I'd like to migrate this to a better doc on the wiki. Cheers, -- Jonathan Perkin - Joyent, Inc. - www.joyent.com ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125 Powered by Listbox: http://www.listbox.com
