Subject: Re: -current currently safe for -cobalt?
To: Brian McEwen <bmcewen@comcast.net>
From: Justin Newcomer <liquidice5@gmail.com>
List: port-cobalt
Date: 10/28/2005 12:12:06
I have always been running -current for pkgsrc on my cobalt, and while
i have come across some issues with samba not compiling the same on
the cobalt as it does on my 386 box,
but thats another time, another issue (in the end, it still works, mostly)
NetBSD caspar 3.99.3 NetBSD 3.99.3 (QUBE) #1: Mon May 9 17:47:51 EDT
2005 root@vmware:/usr/obj/sys/arch/cobalt/compile/QUBE cobalt
and i update my pkgsrc-current weekly via cron.
so... you should be fine? especially since the new pkgsrc digest just
came out, you should at least update to the new release
On 10/28/05, Andy Ruhl <acruhl@gmail.com> wrote:
> On 10/28/05, Brian McEwen <bmcewen@comcast.net> wrote:
> > At 10:34 AM 10/28/2005, you wrote:
> >
> > >If I understand what you're asking, then it's OK to run any level of
> > >pkgsrc with any level of NetBSD. pkgsrc is supposed to be platform and
> > >OS independent. Just as long as you know what level of pkgsrc you are
> > >running, and what level of kernel you built stuff with, etc (but this
> >
> > Well, perhaps worded poorly.
> >
> > I was thinking more along the lines of:
> > Is today a good time to do a complete cvs update of pkgsrc -current :)
> > Or should I wait for any known issues to be corrected.
>
> Ok, I'm not too good at that kind of question.
>
> I've been using pkgsrc since before there were branches for it, so
> I've always used -current and if there are problems I just deal with
> it however I can. So I'm not the best one to answer that.
>
> Andy
>