[DPorts] The only packages available are for DragonFly 3.4

[Justin Sherrill]

If there's packages that build correctly and have no dependencies on
any failing package, why not update them? Is it because the rsync is
set to clear out unmatched packages at the destination, or is there
another reason?

I'd hate to think some arbitrary broken package with, say, 50
dependencies keeps updates from happening for the other 19,950
packages.

On Thu, Jul 25, 2013 at 2:25 AM, John Marino <dragonflybsd at marino.st> wrote:
> On 7/25/2013 05:55, Justin Sherrill wrote:
>> On Wed, Jul 24, 2013 at 2:01 AM, John Marino <dragonflybsd at marino.st> wrote:
>>
>>> For example, yesterday textproc/rasqal broke on dports
>>> because of a curl update.  Had curl been pushed as soon as it built, it
>>> would have broken basically everything KDE4.  But I'll fix rasqal and
>>> restart the "staged" builds until most everything proves to build, and
>>> only then does the entire set to pushed to dports master branch.  This
>>> is how we avoid the breakage typically seen on pkgsrc.
>>>
>>> However, between pushes dports master is static and continuous
>>> incremental builds on a static repository don't do much.
>>
>> Is it possible to have builds go and upload even when there's some
>> number of broken packages? i.e. if most of KDE4 is broken, can
>> everything else not dependent on it be built automatically and
>> uploaded?  This would keep more packages up to date without increasing
>> the workload on you to manually fix and upload.  I'm wary of burnout.
>
> It would result in less packages.
> All the previous versions of the packages that didn't build would be
> deleted during the rsync.  You'd drop from 20,500 package to 16,000
> packages instantly.
>
> It has to be done correctly.