old ports/packages

[Julian Elischer]

On 4/05/2016 1:54 AM, Kevin Oberman wrote:
> On Mon, May 2, 2016 at 11:31 PM, Mathieu Arnold <mat at freebsd.org 
> <mailto:mat at freebsd.org>> wrote:
>
>
>
>     +--On 3 mai 2016 12:02:13 +0800 Julian Elischer
>     <julian at freebsd.org <mailto:julian at freebsd.org>> wrote:
>     | On 2/05/2016 8:39 PM, Mathieu Arnold wrote:
>     |> +--On 2 mai 2016 18:39:57 +0800 Julian Elischer
>     <julian at elischer.org <mailto:julian at elischer.org>>
>     |> wrote:
>     |> | Hi guys,
>     |> |
>     |> | ok so I see:
>     |> |
>     |> | 2014-04-30 ports-mgmt/pkg_install: Replaced by ports-mgmt/pkg
>     |> |
>     |> |
>     |> | So now how do enterprises maintaining appliances etc.
>     generate packages
>     |> | for old systems?
>     |>
>     |> There is a tag,
>     https://svnweb.freebsd.org/ports/tags/PKG_INSTALL_EOL/
>     |> that gives you the last version to support pkg_install. 
>     Anything after
>     |> that will not work with it.  At all.
>     |>
>     | I'm not looking to produce old packages of the ports tree.. I
>     know the
>     | ports crew would hate me for that.
>     |
>     | What I object to is not having the tools needed to generate MY OWN
>     | PACKAGES in ports.
>
>     You can generate your own packages from the ports tree, just not
>     with
>     pkg_install, it was deprecated three or four years ago, and
>     remove 19
>     months ago.
>     The best way to generate packages is with ports-mgmt/poudriere,
>     it will
>     generate a very nice pkg repository.
>
>     --
>     Mathieu Arnold
>
>
> You might also look at ports-mgmt/synth. It is far simpler than 
> poudriere. While lacking any of the enterprise capabilities of 
> poudriere, it is a simple tool to support a modern, local pkg 
> repository of packages for distribution or to support locally 
> modified ports or ports that need to be built with non-standard options.
>
> From synth(1):
> "    The synth program is an advanced concurrent ports building tool 
> aimed at
>      system administrators that prefer or require the building of 
> packages
>      from source rather than installing official binary packages.  
> synth will
>      build packages in a clean environment exactly mirrors the 
> system that
>      they are built on, it will create local package repositories 
> and install
>      pkg(8) repository configuration file that causes locally built 
> packages
>      to be used with the highest priority, all while allowing the 
> system to
>      fully upgraded with a single command."
>
> Its major issue with some is that it is written in Ada, but I just 
> install the package for synth and never bother with building the Ada 
> compiler.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman at gmail.com <mailto:rkoberman at gmail.com>
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

SO if I have an infrastructure that uses old style packages to deliver 
data and configuration information to appliances in the field,

how does synth help me?