From owner-freebsd-ports@freebsd.org Thu Jan 5 13:25:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2045CA0F85 for ; Thu, 5 Jan 2017 13:25:14 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mail.irealone.com (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 890291B73 for ; Thu, 5 Jan 2017 13:25:13 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mail.irealone.com (Postfix, from userid 58) id 456B57938; Thu, 5 Jan 2017 14:25:05 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-100.0 required=5.0 tests=ALL_TRUSTED, LOCAL_TO_FBSD_PORTS autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mail.irealone.com (Postfix) with ESMTP id E85577934 for ; Thu, 5 Jan 2017 14:25:04 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 05 Jan 2017 14:25:04 +0100 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Ports' tips and gotchas Organization: Acheron Media In-Reply-To: <90D33B47-81F9-4C74-8D0B-76F75EC63BF1@gmail.com> References: <76519193d791325700c3beb34b8f447b@acheronmedia.com> <90D33B47-81F9-4C74-8D0B-76F75EC63BF1@gmail.com> Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 13:25:14 -0000 On 2017-01-04 23:59, Ben Woods wrote: > A thought: should the wiki namespace follow the ports namespace, to > avoid any ambiguity? Good advice, and it's a better way to organize them, yes. I did the changes, but there's now another problem and that's we can't have 1:1 mapping between wiki page and port. For example this Postgres tips page I have, it's basically for all postgresql servers in the tree, 92,93,94,95 and 96. So the page is /databases/postgresql which is not directly mapped. Meaning, there will be problems automating links between port origin and wiki page, but I guess we can cross that bridge when we get to it :) I'm not that familiar with moinmoin, maybe there's a way to specify aliases or something. -- Vlad K.