From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH] gnu: add kicad Date: Mon, 23 May 2016 00:13:19 -0400 Message-ID: <20160523041319.GA10803@jasmine> References: <20160215084046.62d5307a@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36772) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b4hFT-0002V7-3D for guix-devel@gnu.org; Mon, 23 May 2016 00:13:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b4hFO-0008F6-PQ for guix-devel@gnu.org; Mon, 23 May 2016 00:13:45 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:56506) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b4hFN-0008AG-40 for guix-devel@gnu.org; Mon, 23 May 2016 00:13:42 -0400 Content-Disposition: inline In-Reply-To: <20160215084046.62d5307a@scratchpost.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: guix-devel@gnu.org On Mon, Feb 15, 2016 at 08:40:46AM +0100, Danny Milosavljevic wrote: > this patch adds kicad, an electronics design automation tool, to "engineering.scm". Cool, I would really like to offer KiCad in Guix. This fell through the cracks but I'd like to resurrect it! Danny, are you still interested in working on it? Here are some comments... > +(define-public kicad > + (uri (string-append > + "https://launchpad.net/kicad/4.0/kicad-" > + version > + "/+download/kicad-" > + version > + ".tar.xz")) It seems they changed the URL format. This works for me now: https://launchpad.net/kicad/4.0/4.0.2/+download/kicad-4.0.2.tar.xz Also, the quoted URL string should start on the same line as string-append. > + (arguments > + '(#:tests? #f ; TODO re-enable Do you remember the state of the tests? Was it just a few that failed? > + #:configure-flags I noticed on the KiCad download page [0] some instructions to set the version string, and other useful build-time configurations. Do you think it would be appropriate to apply them? ------ For the moment you are supposed to use the following options to set the version string: -DKICAD_REPO_NAME=stable -DKICAD_BUILD_VERSION=4.0.2 And you encouraged to enable the python scripting, even though it is not enabled by default with the following additional Cmake options. -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON ------ > + (list "-DKICAD_SKIP_BOOST=ON" ; use system boost; otherwise, it tries to download one and fails. > + ; TODO -DCMAKE_BUILD_TYPE=Release > + ; TODO -DOPENSSL_ROOT_DIR=... > + ; TODO -DCMAKE_PREFIX_PATH=... > + ; TODO -DCMAKE_INSTALL_PREFIX=... > + ; TODO -DDEFAULT_INSTALL_PATH=... > + ; TODO -DKICAD_SCRIPTING=ON > + ; TODO -DKICAD_SCRIPTING_MODULES=ON > + ; TODO -DKICAD_SCRIPTING_WXPYTHON=ON What features are missing without them? What is OpenSSL / TLS support used for? > + ; TODO optional doxygen for source docs Do we just need to add doxygen to native-inputs? > + (inputs [...] > + ("libressl" ,libressl) Unusual choice but I don't object to it. This would be the first package to refer to libressl in our tree. > + (description "Electronics Design Automation Suite") This should be more descriptive in the final patch. > +; TODO extra options for Python (which) and for version. Ah, I see you noticed the text on the download page :) > +; TODO kicad-doc, kicad-library, kicad-footprints Do we need to add the library and footprints at the same time as KiCad itself, or can they come later? We should try to offer the docs from the start. [0] http://kicad-pcb.org/download/source/