Personally I'm running my own repo too. I'd suggest you to have a simple
web server ( apache, nginx, whatever you like). The URL/directory name you
will choose is up to you but keep in mind that might want to have multiple
architecture/ os version/pkgsrc versions. The only magic you'll need for
pkgin is to create a pkg_summary. I have create a quick script that does it
:
#!/bin/sh
PACKAGE_DIR=/srv/data/packages/All
cd $PACKAGE_DIR
find . -name '*.tgz' -exec pkg_info -X {} \; > pkg_summary
gzip -c pkg_summary > pkg_summary.gz
bzip2 -z pkg_summary -k -f
On Tue, Jan 28, 2020 at 12:33 PM Ronald Georgia <[email protected]> wrote:
> Greg,
> Hmmm... now this sounds interesting. Definitely some fodder to chew
> on. Thank you.
>
> This is one major reason why I love NetBSD... the community!
>
> On Tue, Jan 28, 2020 at 11:52 AM Greg Troxel <[email protected]> wrote:
> >
> > In addition to what Brad said, you can use something like this
> >
> > cd $HOME
> > mkdir -p FUSE
> > mkdir -p FUSE/All
> > mount_psshfs [email protected]:/usr/pkgsrc/packages/All /home/foo/FUSE/All
> >
> > to make them available over ssh. See the manpage of course.
>
>
>
> --
> Ron Georgia
> “90% of my problems are due to ignorance, the other 10% is because I
> just don’t know any better.”
>
