From owner-freebsd-questions@freebsd.org Sun May 31 01:39:00 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 046002FE40C for ; Sun, 31 May 2020 01:39:00 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49ZLYs5pzvz461H; Sun, 31 May 2020 01:38:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([178.12.46.193]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPA (Nemesis) id 1MnaY1-1jFoKm0SDF-00jadA; Sun, 31 May 2020 03:38:53 +0200 Date: Sun, 31 May 2020 03:38:52 +0200 From: Polytropon To: Brandon helsley Cc: Matthew Seaman , "freebsd-questions@freebsd.org" Subject: Re: FreeBSD Cert Message-Id: <20200531033852.9c345a6b.freebsd@edvax.de> In-Reply-To: References: <626d9ab4-b00b-6112-8697-ea972eceb5b2@heuristicsystems.com.au> <8696720e-3c03-8ffa-6b2c-4c4c98772a49@FreeBSD.org> <20200531005421.8f845320.freebsd@edvax.de> Reply-To: Polytropon 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 X-Provags-ID: V03:K1:iHL6wAzX1EfVMKbQglgUTzvyB19nzKEOWu3XaxCOW5eilPf9IvM Q2bx2svkBAbzS86XNDEggvr0I53vO3In9dhoTY1saVPj8hXiw3esm2p9RYVQlaxUDPX5FAa rl4Rjg0E9zLtcIwiCVlZ02ujFuywYeGLsToNRJbs+6rseeqyaDGd2qGJdjKzwwraug+wsY9 boKyOjQYnBI16MaRack+g== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:AOMc2mJFNHI=:x8GZlbTbcJVmV8Vbr4Yv1m PZXnL7SnbjXKCyyN5DueM8M+wTfega+peW6G/sV3mLfQaDyQuS59lfFDs1BCfN7+f2IRfBSL4 JZ5TMIMydcLxxZ1kifPPvcIgC2hTLbP/w6wlgSGSw9vflrrR3c0pZT8oul7XcjPNXQnYBJheW xpz9KmGscPDKx58AfIGNitCw/R7r05nxJUT55KNgSzblzjflIXh/IWFgjwkQCSAT3OTYCRePT F+bvPztbk+4eJHKVxZC0H0aLuT0ocxawxi61i5pt6cxP1hoT6ucxAVV5hUfRpvVKGCu7WWMC+ V9TDmsij3pTqwKxl8oyFapPSC6rNdizDwTLcoO7ra29JZWn+ZY9PYV93o2tKsRoDu9Pp/AvDm apIYFLTeSZ/2Pjl3cAU6FD6EeKhGfPJhGgByBzmGmkKSWWBU5BfRHa9RdzWpVecsB7XXqNPBn KgjNqM5InjHPo6CEkOcCUvOOIz40/XBMiWMXH0UDI80V/vG9anw9Ten/P+UfFgci7xleRkrUq nkUgzbQgJhsvG+rYVTX8wPyliGvYcebUnMMbrzh4lTetXOiHxCHvzP5nk+4zQZzniL/zjfC0k hrcORrVMAt56U67TVrs4Kpq3LDgGl0Y7BK0r9Z1Ok2rsNqnipFcQZzcrkkgDyR4EkyubJ76D2 uoELhQ1N0eWhHxMzow1uHgcgJNKklplyN5zU1Xds4q/75Mv7BMZRjeQNgO1XGwAJRJ7Lmwl3F 1PgMXNIpY4ccRiOj2OmiuWuNOOl7zFzXC6O+QiWtB2VR120A2YqIXTm9s8uvpjeEr/Hf8K/LU RFDPQ5ru1FgZVKzzkOueZ61GzJd5S9ZxP9vRYFimuS9RWSRMVQ2/bjaqZB3miNNN461nZDMgl w/+nR0uJ60iQjAgr1tIA== X-Rspamd-Queue-Id: 49ZLYs5pzvz461H X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.131) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [3.97 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-0.10)[-0.099]; FREEMAIL_TO(0.00)[hotmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[178.12.46.193:received]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.81)[0.811]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.86)[0.857]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.131:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.126.131:from]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 01:39:00 -0000 On Sat, 30 May 2020 23:03:59 +0000, Brandon helsley wrote: > So to find out the legality of licensing to port a program to > freebsd do all I have to do is contact that programs website. That is the first step to go. For most open source programs, it should not be a big problem to make them available as a FreeBSD port when a Linux version already exists. However, contacting the original author(s) is probably the best thing you can do. In absolutely worst case, you can always contact a legal counsel, if that should be needed. > And then source code is quite easy to obtain I see. Depends. Some projects have their own website where they also publish source code, others use external services like GitHub. I'm also sure there are at least a few which use different services, like their own SVN server or something like that. In certain cases, _no_ source code is distributed (for example the nVidia graphics driver published by nVidia is just a binary blob, embedded as a port, so building the port does not compile anything, instead it just creates a package from an existing set of binary files). > It would just be on git hub right. At least today, that would surely be the most common way. > For the executable script and profiles and config files l, > I guessing the porters handbook is how you fashion those > in working order? Correct. Understand a port as a "cooking recipe" that describes where to obtain program sources from, how to patch them, how to build them, and where to install the results to. That kind of "recipe" is standardized - it's more or less the same approach for all ports. The result of following that "recipe" usually is a package that can be installed with pkg (and "make install" does exactly that). Note that there are a few ports where the licensing terms do not allow distribution in binary form - such ports cannot be installed via "pkg install", instead you always have to build them from source. This aspect is alco controlled by the "recipe". The FreeBSD Porter's Handbook provides an excellent foundation on how all those things work, from file description, their meaning and content, which tools and procedures, up to how the results of building a port are structured. So I'd suggest that reading this specific piece of documentation is essential for anyone who wants to become a port maintainer. You simply cannot get it working without it. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...