From owner-freebsd-ports@FreeBSD.ORG  Thu Aug 21 16:01:37 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6C51816A4BF
	for <ports@FreeBSD.org>; Thu, 21 Aug 2003 16:01:37 -0700 (PDT)
Received: from fsp1.physik.ruhr-uni-bochum.de (fsp1.physik.ruhr-uni-bochum.de
	[134.147.168.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D5D5A43FBD
	for <ports@FreeBSD.org>; Thu, 21 Aug 2003 16:01:36 -0700 (PDT)
	(envelope-from strattbo@fsp1.physik.ruhr-uni-bochum.de)
Received: by fsp1.physik.ruhr-uni-bochum.de (Postfix, from userid 514)
	id 56D80243EE; Fri, 22 Aug 2003 01:02:41 +0200 (CEST)
Date: Fri, 22 Aug 2003 01:02:41 +0200
To: ports@FreeBSD.org
Message-ID: <20030821230241.GA19471@fsp1.physik.ruhr-uni-bochum.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
From: strattbo@fsp1.physik.ruhr-uni-bochum.de (Thomas Stratmann)
Subject: e2fsprogs 1.32 working partly - should this import?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2003 23:01:37 -0000

Hi crowd,

I was a bit too quick with my posting from yesterday - I do not have
gotten e2fsprogs version 1.32 working. But what I do have is this:
I altered the e2fsprogs port directory to update to 1.32, and as far as
I can see (I read the porters-handbook by now) it is a valid port.

fsck.ext2 works for me (and saved my life, now I can multiboot into my
linux again). All other major tools from the package probably don't
work. I only checked mke2fs, it is unable to get the device size
probably (some wrong iocontrol?).

AFAIK, this is the same with the old (1.27) version of the port.
The only difference: 1.27 couldn't check my filesystem due to
'unsupported extensions', which the new version seems to handle.

So, if I got everything right, the new port would still be broken,
but anyways an improvement.

Guys (and Girls), what is the right policy in this situation? Should I
submit the new version as a PR anyway? If so, is there anything special
I should pay attention to?

I'd appreciate if you'd answer privately, I'm still not on this list.
I consider subscribing if I find myself doing this more often...

Cheers,
Thomas