From owner-freebsd-questions@FreeBSD.ORG Wed Mar 19 08:45:54 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6E6D564 for ; Wed, 19 Mar 2014 08:45:54 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A8910838 for ; Wed, 19 Mar 2014 08:45:54 +0000 (UTC) Received: from r56.edvax.de (port-92-195-67-138.dynamic.qsc.de [92.195.67.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id EEF542765A; Wed, 19 Mar 2014 09:45:51 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s2J8jRno002116; Wed, 19 Mar 2014 09:45:27 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 19 Mar 2014 09:45:27 +0100 From: Polytropon To: Matthew Pherigo Subject: Re: lang/nimrod doesn't compile anything [SOLVED] Message-Id: <20140319094527.254a8fd2.freebsd@edvax.de> In-Reply-To: References: <85FE6DC9-3D0D-4AAE-BEF7-5F0649DE1E14@gmail.com> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 08:45:55 -0000 On Tue, 18 Mar 2014 22:32:48 -0500, Matthew Pherigo wrote: > Hey all, > > After some googling that I didn't think to do before, > I was able to fix it! For the future problem-sufferers, > here's what's going on. Apparently, does not look for > its configuration file in anything other than /etc/nimrod.cfg. > A simple ln -s fixed it. That surely is an intermediate solution, but far from perfect or even "accepted". The /etc directory is reserved for system files (of the OS), and nimrod is an additional package, so according to "man hier", it should have its configuration files in /usr/local/etc. Either should an environmental variable or a command line option be present, but it will probably be a better idea to write to the maintainer and ask him to fix this bug. The symlink you've created is not recorded by any means of packaging tools, so if you update or remove things, it will be left, possibly causing trouble later on which nobody can imagine at the moment. What you're seeing seems to be a typical "Linuxism". :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...