old ports/packages

[Julian Elischer]

On 3/05/2016 2:31 PM, Mathieu Arnold wrote:
>
> +--On 3 mai 2016 12:02:13 +0800 Julian Elischer <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>
> |> 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.
>
Of course I can create NEW packages..  I want to generate OLD style 
packages..

what's so hard to understand about that?  if a company has old 
packages build into it's infrastructure....

and has to create old style packages of "proprietary stuff" to send 
out to appliances out in the field then you are breaking them.