From owner-svn-ports-head@FreeBSD.ORG Wed Sep 10 10:36:08 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE747A5E for ; Wed, 10 Sep 2014 10:36:08 +0000 (UTC) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89B351B68 for ; Wed, 10 Sep 2014 10:36:08 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id jd19so540774oac.25 for ; Wed, 10 Sep 2014 03:36:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hCbGK+Jty17dD590p03nUcMr5I+FNpuDUH514v5ik4M=; b=h8yDo9fMDvUYTBWrZiCQyymHbCINMWcD/OB4Ht7b+Jsx5Ytbios3rFfe0MFUnDHwig OJNMMaGcjSVt0apepskQAW+nW89tpPwJeVnnCwRLIR5w5cjj4Z0Z4b5/gGAExP/t9cHy fB5+Kbh7XF4E+QhMzBK2yDeJe/U23PP8Cwc7k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hCbGK+Jty17dD590p03nUcMr5I+FNpuDUH514v5ik4M=; b=Hv+e6Z95qjz5VQy0Ehog+U8EcmBXMZ6pnF/V9M1VbOUkslK5q1y+7yG/LLVLwCZOCg Pj2b/VUMim5wKeKZneBTam3XRHYcuq5TjHRiEJ2wXAaVPUcIWYm1Bm5KPIwFXuDAdrSj JTmuXPk4eJJdWnmRFgfXRZf7QnYKvCBFvQcnNXUYkL8pn+SM3A4RqaCw3PrMNXOdGmvN yATaPO+x3D+I5id4os94UHEpFj4tdYrKjGMONR9pLQB/AeZl5WyjLuI6yyJWdFAo5kUT VHSMMdS0Cnr5bZCE+axAvRjZBoMVGuX7c+K7Dro4zXDyz1RJKbGegWuFLgKnInru33Ju RRIw== X-Gm-Message-State: ALoCoQn4knvdw6g+JqIFcFodT1snuq8W5dExy8fdgTtK8Aq4n3bGunhpFZIKXnt3dvDKAB8BLSt9 MIME-Version: 1.0 X-Received: by 10.182.87.167 with SMTP id az7mr44848531obb.41.1410345367575; Wed, 10 Sep 2014 03:36:07 -0700 (PDT) Received: by 10.76.141.136 with HTTP; Wed, 10 Sep 2014 03:36:07 -0700 (PDT) X-Originating-IP: [213.162.68.209] Received: by 10.76.141.136 with HTTP; Wed, 10 Sep 2014 03:36:07 -0700 (PDT) In-Reply-To: <540F716D.8020001@marino.st> References: <201409091918.s89JIStw037486@svn.freebsd.org> <540F6D8A.30907@marino.st> <540F704B.7070209@FreeBSD.org> <540F716D.8020001@marino.st> Date: Wed, 10 Sep 2014 12:36:07 +0200 Message-ID: Subject: Re: svn commit: r367769 - in head: . emulators emulators/virtualbox-ose-kmod-legacy emulators/virtualbox-ose-legacy From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= To: John Marino Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Bryan Drewery , ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 10:36:08 -0000 Am 09.09.2014 23:30 schrieb "John Marino" : > > On 9/9/2014 23:25, Bryan Drewery wrote: > > virtualbox-ose-kmod-legacy does not have a dependency on unstaged > > emulators/virtualbox-ose-legacy. Naturally decke@ was not notified. > > Okay, so the issue is the kmod port? > I didn't realize it had a function by itself, I thought it existed > solely for virtualbox-ose-legacy. > > > > It is not proper to remove a port without a deprecation period if it > > works and has no other reason to be removed. > > > > btw decke@ still is a portmgr. > > > The language is inexcusable. Yes it is. Sorry did not want to get rude. > If virtualbox-ose-kmod-legacy is useful by itself, I'm happy to restore it. I am quite sure nobody would use the kmod port on it's own - nevertheless I would expect someone to mark ports as deprecated/expired and/or reset maintainer like we have done so for ages. Is this really the way we want to handle that? Deleting the port means we will not build any packages for the next week and many users will be surprised at least. I am currently on holidays so I won't be able to fix it in the next couple of days. Yes, I am aware that the staging deadline has passes and I have staged all my ports already but still this one port seems to have gone unnoticed - for whatever reason. I will do my work to get it fixed but it will take a few days.