svn commit: r373476 - in head: . Mk/Uses lang/perl5.14 lang/perl5.14/files lang/perl5.16 lang/perl5.16/files lang/perl5.18 lang/perl5.18/files lang/perl5.20 lang/perl5.20/files
Alex Kozlov
alexkozlov0 at gmail.com
Thu Nov 27 10:53:40 UTC 2014
On Thu, Nov 27, 2014 at 11:16:49AM +0100, Mathieu Arnold wrote:
> +--On 27 novembre 2014 12:06:13 +0200 Alex Kozlov <alexkozlov0 at gmail.com>
> wrote:
> | On Thu, Nov 27, 2014 at 09:57:39AM +0000, Mathieu Arnold wrote:
> |> Author: mat
> |> Date: Thu Nov 27 09:57:39 2014
> |> New Revision: 373476
> |> URL: https://svnweb.freebsd.org/changeset/ports/373476
> |> QAT: https://qat.redports.org/buildarchive/r373476/
> |>
> |> Log:
> |> - Bring back the .packlist files, many people need them, they will
> |> automatically added to the plists.
> | How many people need them, and for what?
> | I'm genuinely puzzled.
> Many people emailed me since yesterday, the fact that FreeBSD does not
> break the modules distribution means they can use the ports to maintain the
> module they need and use tools like App::FatPacker to bundle their scripts
> for deployment.
Hmm, AFAIK, using .packlist(s) isn't preferable method for FatPacker/PAR,
not least because many vendors remove them.
Current recommendation for FatPacker is:
$fatpack trace myscript.pl && fatpack packlists-for `cat fatpacker.trace` >packlists && \
fatpack tree `cat packlists`
--
Alex
More information about the svn-ports-all
mailing list