From owner-freebsd-ports@FreeBSD.ORG  Sun Feb 21 08:01:41 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0B2501065679
	for <ports@FreeBSD.org>; Sun, 21 Feb 2010 08:01:41 +0000 (UTC)
	(envelope-from kamikaze@bsdforen.de)
Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79])
	by mx1.freebsd.org (Postfix) with ESMTP id B72FD8FC18
	for <ports@FreeBSD.org>; Sun, 21 Feb 2010 08:01:40 +0000 (UTC)
Received: from mobileKamikaze.norad (unknown [88.130.201.172])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.bsdforen.de (Postfix) with ESMTP id 37A1B8A16A5;
	Sun, 21 Feb 2010 09:01:25 +0100 (CET)
Message-ID: <4B80E851.5000103@bsdforen.de>
Date: Sun, 21 Feb 2010 09:01:21 +0100
From: Dominic Fandrey <kamikaze@bsdforen.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-GB;
	rv:1.9.1.7) Gecko/20100216 Thunderbird/3.0.1
MIME-Version: 1.0
To: portmgr-feedback@FreeBSD.org
References: <20100221073016.695E21CD39@mail.droso.net>
In-Reply-To: <20100221073016.695E21CD39@mail.droso.net>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ports@FreeBSD.org, linimon@FreeBSD.org
Subject: Re: FreeBSD ports which are currently scheduled for deletion
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
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: Sun, 21 Feb 2010 08:01:41 -0000

On 21/02/2010 08:30, linimon@FreeBSD.org wrote:
> portname:           java/eclipse-emf
> description:        Eclipse Modeling Framework
> maintainer:         freebsd-eclipse@FreeBSD.org
> deprecated because: This plugin can be installed from within eclipse via
>                     the updater
> expiration date:    2010-01-19
> build errors:       none.
> overview:           http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-emf
> 
> 
> portname:           java/eclipse-gef
> description:        Graphical Editing Framework for the Eclipse IDE
> maintainer:         freebsd-eclipse@FreeBSD.org
> deprecated because: This plugin can be installed from within eclipse via
>                     the updater
> expiration date:    2010-01-19
> build errors:       none.
> overview:           http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-gef

It is my conviction that these updaters only exist, because
Microsoft OSs come without a packaging system.

I prefer to have my plugins installed once and maintained by the
system administrator instead of delegating this task to each
user, such multiplying disk use and work. I'm aware I could
do this by running eclipse as root, but I shudder at the thought
of such abominal behaviour.

I'm willing to take maintainership to preserve my ideal of using
one packaging system for all software.

Should I write a PR?

Regards

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?