How do I build my own package server?

Bertram Scharpf lists at
Tue Jun 24 13:55:09 UTC 2014


this is sort of what I did until now:

  Inside a jail:

  - SVN-Update "/usr/ports".
  - Merge my own patch files for several packages.
  - Find the outdated ports using a self-written tool.
  - Do "make clean" and "make package" for them.
  - Build a package list.

  On all other machines and jails:

  - Load the package list.
  - Find the outdated packages.
  - Do "pkg_delete" and "pkg_add" for them.

Now, the pkg_* tools are no longer supported! Rewriting my update tools
would take at least two days and I have better things to do. On the
other side, I doubt whether it would go any faster learning some
portmaster or portupgrade tool until I find the features I need.
(Actually, I tried portmaster and soon was tired of seeing it
redundantly cleaning and recompiling ports.)

Therefore my question: Is there any documentation how to build a package
server that can be understood in finite time?

On the other side: I do not feel very well having loads of SQLite
databases in the base system. Could it be worth the effort to further
develop the traditional pkg_* tools?

Thanks in advance,


Bertram Scharpf
Stuttgart, Deutschland/Germany

More information about the freebsd-questions mailing list