On Wed, March 26, 2008 10:46 am, Hasso Tepper wrote:
> * Regular builds of pkgsrc HEAD on both our stable and HEAD with info
> about failures made available for community. I think that many of us
> (including me) can take a look at logs and try to fix issues. The
> important point is that we
Matthew Dillon wrote:
... What we would do is set up an automatic daily sync
from NetBSD to our pkgsrc CVS so we would always have the latest, but we
would also have the option of committing fixes into our tree to get
them off our table...
That's a great idea. I would have
> * Patches sit in NetBSD bugs database too long. Nobody seems to confident
> enough to commit patches or just don't care enough or patches remain
> just unnoticed etc. #36978 is good example, but there are others
> (net-snmp with this fix doesn't build any more, btw, but I'm also afraid
:> * Regular builds of pkgsrc HEAD on both our stable and HEAD with info=20
:> about failures made available for community. I think that many of us =
:
:> (including me) can take a look at logs and try to fix issues. The=20
:> important point is that we should try to catch as much of bugs as
On Wed, Mar 26, 2008 at 9:46 AM, Hasso Tepper <[EMAIL PROTECTED]> wrote:
> * Patches sit in NetBSD bugs database too long. Nobody seems to confident
> enough to commit patches or just don't care enough or patches remain
> just unnoticed etc. #36978 is good example, but there are others
> (n
Hasso Tepper wrote:
At least some of us agreed that pkgsrc isn't shiniest package management
system - upgrade is real pain etc. This is not about these technical
issues. Pkgsrc is IMHO the best option we have at the moment, but ...
Pkgsrc is virtually the only option we have at the moment.
AF
Thomas E. Spanjaard wrote:
> Fixed in pkgsrc -current, and possibly 2008Q2 as well? The problem was
> some bluetooth preprocessor directives had a conditional only for
> NetBSD, but we use NetBSD's bluetooth stack as well.
Yeah, which reminds me that IMHO we should discuss _the_ issue with pkgsrc
