Update to the state of the pkgsrc

[Justin C. Sherrill]

On Tue, September 29, 2009 2:56 am, Hasso Tepper wrote:

> - Official (signed?) regular pbulk builds. The current situation really
>   isn't acceptable. I'd never use packages from random source updated
>   randomly (no security updates). Really.

This I don't know how to do, and a few seconds of googling don't explain. 
Can you or someone point me at what having signed packages entails?  MD5
sums for all binaries?

I'm working on the more regular builds thing.  My biggest obstacle is time
- I can only work on this at the end of the day, so there's 24 hours
between trying something and seeing if it worked in the best of
circumstances.  In worst case, it takes more than a week (a full build).

> - Public logs from all pbulk builds. The logs are there for reason. I
>   don't see any in the avalon at the moment. How people should fix
>   anything even if they care?

I'll work on getting this into (out of?) the automated builds.

> - Using bug tracking systems for pkgsrc bugs. I'd recommend using NetBSD
>   GNATS for bugs which are addressed to the pkgsrc committers à la "here
>   is a patch to make package x/y build on DragonFly" and
>   bugs.dragonflybsd.org for reports which need to be investigated by
>   DragonFly developers (à la "the package x/y doesn't build or work on
>   DragonFly").

I think if we (meaning DragonFly-using people) communicated more to
general pkgsrc developers, it would help.  I've been watching traffic on
the pkgsrc-users lists for a while, and when people describe problems with
packages on DragonFly or elsewhere, I see it addressed.