On Tue, 29 Jul 2008 14:53:14 +0100
Alistair Crooks <[EMAIL PROTECTED]> wrote:
> We don't have portupgrade, but there are a number of other ways of looking
> at the problem.
>
> 1. "make update" - looks at all the packages installed, including
> 2. "make replace" - addresses the problems with "m
:...
:2. "make replace" - addresses the problems with "make update" by going
:
:3. "pkg_rolling-replace" - the nearest thing to automating this scheme.
:
:4. Use pkg_comp to build packages in a chroot environment, and then have
:...
:Hope that helps,
:Alistair
This brings up a pet peave of min
On Mon, Jul 28, 2008 at 12:12:29AM +0300, Cristi Magherusan wrote:
> Hello,
> On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote:
> > The pkgsrc-2008Q2 Branch
> >
> >
> > The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2
> > branch, which has sup
Hi,
* Jordan Gordeev wrote:
>
> I think it's a good idea to have a "Making a new release" document which
> lists all the steps that are necessary for making an official release
> including all the places where the new release should be noted.
We already have such a document:
http://www.drago
Michael Neumann wrote:
Hi,
The release-src-cvsup target still contains the RELEASE_1_12 tag,
which should instead be:
-rDragonFly_RELEASE_2_0_Slip
I don't know where to find this file in the source tree, so I can't
fix it myself. Anyone?
Regards,
Michael
I think it's a good idea to h
