We can do that - the caveats are that John is building pkgsrc-current,
so you have to be on pkgsrc-current to use them.  We release DragonFly
with the current quarterly release of pkgsrc, so by default, people
are not going to pull from his collection of files even if they are
uploaded.

There also can be regressions; packages that were working may break
due to changes in pkgsrc-current as updates happen, so someone moving
from a quarterly release to pkgsrc-current may find something doesn't
upgrade when previously it did just fine.  John is so astonishingly
active in fixing issues that's unlikely, but it is remotely,
temporarily, possible.

These aren't reasons against doing it; I'm mentioning it because it
added complexity to a process that isn't as streamlined as I'd like it
to be.

On Sun, Aug 19, 2012 at 2:10 AM, John Marino <dragonfly...@marino.st> wrote:
> On 8/18/2012 00:44, Pierre Abbat wrote:
>>
>> On Wednesday 15 August 2012 13:35:23 John Marino wrote:
>>>
>>> This was a full run, nothing was masked.  We're over 11,700 packages for
>>> now (96.4%).  The build logs are available this time, see link below.
>>> Most of the regressions have already been fixed by their maintainers and
>>> Asterisk 10 should build cleanly next time.
>>
>>
>> Where should I point pkgin? I checked the usual location and there are no
>> packages for i386.
>>
>> Pierre
>>
>
> So far I don't upload packages, I'm just doing private build runs to help me
> determine what needs fixing.  These aren't "official" packages.
> Unless Justin instructs me to start uploading...
>
> John

Reply via email to