On Tue, Apr 1, 2014 at 11:38 AM, Matthew Seaman matt...@freebsd.org wrote:
This is why the quarterly branches exist. 2014Q1 (Just EoL'd) and
2014Q2 (just branched from head) will now get only security and port-fix
type upgrades for the next 3 months. Therefore if your poudriere repo
had been
On Wed, Apr 2, 2014 at 6:41 AM, Mathieu Arnold m...@freebsd.org wrote:
+--On 1 avril 2014 11:18:05 -0400 J David j.david.li...@gmail.com wrote:
| from perl-5.12.3.4_5a to 5.12.3.4_5a1.
Perl 5.12 has been removed about a month and half ago, so, if you were
still using it, it's going to be a
+--On 3 avril 2014 11:05:49 -0400 J David j.david.li...@gmail.com wrote:
| On Wed, Apr 2, 2014 at 6:41 AM, Mathieu Arnold m...@freebsd.org wrote:
| +--On 1 avril 2014 11:18:05 -0400 J David j.david.li...@gmail.com
| wrote:
| | from perl-5.12.3.4_5a to 5.12.3.4_5a1.
|
| Perl 5.12 has been removed
If your ports tree is managed by subversion, you can just selectively
update foobar's directory. As long as it doesn't depend on a specific
version of perl, poudriere will see that it is updated and perl is
not.
On Thu, Apr 3, 2014 at 10:36 AM, Mathieu Arnold m...@freebsd.org wrote:
+--On 3
On Thu, Apr 3, 2014 at 11:36 AM, Mathieu Arnold m...@freebsd.org wrote:
Something built for perl 5.14.0 will work with perl 5.14.5.a6_7.
This is one of those things that's true most of the time. And on
those occasions when it isn't, the fallout is spectacular. It does
not come up more often
On 4/3/2014 19:52, J David wrote:
The net effect of all of this is that even if you do take 24 hours and
rebuild all the ports that depend on perl because of that foobar
vulnerability, including bazqux, you *still* end up pissing off the
bazqux users because it rev'd bazqux from 1.5 to 2.0
+--On 3 avril 2014 21:54:52 +0200 John Marino freebsd.cont...@marino.st
wrote:
| I don't think anybody is going to reprogram the logic of poudriere
| though. This is just an academic discussion of what could be done, but
| I doubt anybody wants to actually implement it due to the potential side
|
+--On 1 avril 2014 11:18:05 -0400 J David j.david.li...@gmail.com wrote:
| from perl-5.12.3.4_5a to 5.12.3.4_5a1.
Perl 5.12 has been removed about a month and half ago, so, if you were
still using it, it's going to be a pain, you should upgrade to 5.16.
| - Convince poudriere only to build a
Poudriere and pkgng have been great tools for managing large numbers
of FreeBSD ports.
However, we would like to optimize the build in some cases.
Consider a poudriere-generated pkgng repository with about 10,000
packages in it. Now, just because the FreeBSD ports collection is the
way it is,
On 04/01/14 16:18, J David wrote:
Consider a poudriere-generated pkgng repository with about 10,000
packages in it. Now, just because the FreeBSD ports collection is the
way it is, about 8,000 of those packages are going to depend directly
or indirectly on perl.
Now suppose one of those
01.04.2014 19:18, J David пишет:
- Build port(s) outside of poudriere and then inject them into the
pkgng repo maintained by poudriere?
I'd go this way:
1. Update/install the latest portstree at one system that uses
your custom packages.
2. Build/install/package a new version of the needed
11 matches
Mail list logo
