From owner-freebsd-ports@FreeBSD.ORG Thu Jan 19 18:06:01 2006 Return-Path: X-Original-To: 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 AE62D16A423 for ; Thu, 19 Jan 2006 18:06:01 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12DCB43D4C for ; Thu, 19 Jan 2006 18:06:00 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.1/8.13.1) with ESMTP id k0JI5w0S071063; Thu, 19 Jan 2006 12:05:59 -0600 (CST) (envelope-from sean-freebsd@farley.org) Date: Thu, 19 Jan 2006 12:05:58 -0600 (CST) From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= To: "Michael C. Shultz" In-Reply-To: <200601190943.26432.ringworm01@gmail.com> Message-ID: <20060119115525.O77523@thor.farley.org> References: <20060119101850.F76211@thor.farley.org> <200601190943.26432.ringworm01@gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1291993854-1137693958=:77523" Cc: freebsd-ports@freebsd.org Subject: Re: Old perl-based script to manage ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2006 18:06:01 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1291993854-1137693958=:77523 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 19 Jan 2006, Michael C. Shultz wrote: > On Thursday 19 January 2006 09:24, Se=E1n C. Farley wrote: >> Ok. The subject line is a rip-off of Doug Barton's. :) When I saw >> his message in the archives, I decided to announce my contribution. >> There can never be enough tools to manage ports. :) >> >> I started writing this tool in 2003 when Perl was still in the base. >> It is called Port Manager[1] (one of a few called this), pm.pl >> specifically. It is comparable to portupgrade with a few exceptions >> as listed on the web page. Build error recovery is a big feature. >> >> Although it is not well documented, 'pm.pl -nva' should show what >> would be done to update a system without actually doing it. >> Obviously, -h will provide you with help. A .pmrc can be used for >> options specific to ports and to hold from updating ports. Globals >> for all ports go into /etc/make.conf. I just need to document the >> .pmrc file. > > Can you show where you posted this prior to 2004-04-20 with a > copyright notice? A reference from archive.org (wayback machine) for > example. If you have proof I will change the name of portmanager to > avoid infringing on your copyright and if you don't I insist you stop > infinging on mine. Neither of us are infringing on each others' copyrights since we are not copying each others source. Trademarks are what you are thinking about, and we (at least I) do not have these. > See https://sourceforge.net/project/showfiles.php?group_id=3D107280 for t= he > first official portmanager posting dated 2004-04-20. I first made mention of it on August 24, 2004[1]. We are both eclipsed by the Darwin PortsManager[2]. Se=E1n 1. http://bsdnews.com/view_story.php3?story_id=3D4694 2. http://www.opendarwin.org/pipermail/darwinports/2003-March/016245.htm= l --=20 sean-freebsd@farley.org --0-1291993854-1137693958=:77523--