From owner-freebsd-ports@FreeBSD.ORG Tue Dec 9 17:04:21 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACA011065670 for ; Tue, 9 Dec 2008 17:04:21 +0000 (UTC) (envelope-from wahjava@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by mx1.freebsd.org (Postfix) with ESMTP id 2108F8FC1C for ; Tue, 9 Dec 2008 17:04:20 +0000 (UTC) (envelope-from wahjava@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so28541tib.3 for ; Tue, 09 Dec 2008 09:04:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:to:cc:subject :organization:references:x-face:x-uptime:x-url:x-openpgp-id :x-openpgp-fingerprint:x-os:x-mailer:x-mail-morse:x-attribution:date :in-reply-to:message-id:user-agent:face:mime-version:content-type; bh=znBpxDwvU/mpmUp8IqWV6V6ZznOEDm3IbSlsGd2Zdog=; b=h8ykEnO7IuXE7qGVEoNl0Hvs74YGL5F4neo3Hz+pWn1rh6Xlfac9axcjA3zwMLoLPF 2m1QfYTv6DsRmHvsxekN3VzRtzEoPeLiFUkXCKLJuKT+1RJMraxfo6bNPXsPn8GvoeWW uqrt+bEgMpSJ43bXnUw4VfEFYS+nNMrMHaNGg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:to:cc:subject:organization:references:x-face:x-uptime :x-url:x-openpgp-id:x-openpgp-fingerprint:x-os:x-mailer:x-mail-morse :x-attribution:date:in-reply-to:message-id:user-agent:face :mime-version:content-type; b=Jxxh6fgHjUS90jReVdI9ZpLz+b5m9O1TOJfYCtVBN30etr8AUdrpLMGS0NeZeTZyI3 EWzFp7CbeYjqkkRCNdpwhaJIiNofnj0aMlS1mIRXZXMat37d+e0aSroFyzlNTpqd0hdN TpYEiFVuqX2aWwWfz+ddSOpiM8104K+o5Q0SA= Received: by 10.110.49.6 with SMTP id w6mr437741tiw.23.1228842259334; Tue, 09 Dec 2008 09:04:19 -0800 (PST) Received: from chateau.d.lf ([122.162.55.50]) by mx.google.com with ESMTPS id i9sm486412tid.12.2008.12.09.09.04.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Dec 2008 09:04:17 -0800 (PST) Sender: =?UTF-8?B?4KSG4KS24KWA4KS3IOCktuClgeCkleCljeCksiBBc2hpc2ggU2h1a2xh?= From: wahjava.ml@gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) To: Dmitry Marakasov Organization: alt.religion.emacs References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> X-Face: )vGQ9yK7Y$Flebu1C>(B\gYBm)[$zfKM+p&TT[[JWl6:]S>cc$%-z7-`46Zf0B*syL.C]oCq[upTG~zuS0.$"_%)|Q@$hA=9{3l{%u^h3jJ^Zl; t7 X-Uptime: 22:30:31 up 6:39, 4 users, load average: 0.12, 0.12, 0.15 X-URL: http://wahjava.wordpress.com/ X-OpenPGP-ID: 762E5E74 X-OpenPGP-Fingerprint: 1E00 4679 77E4 F8EE 2E4B 56F2 1F2F 8410 762E 5E74 X-OS: GNU/Linux on Linux 2.6.25-gentoo-r7 kernel on x86_64 architecture X-Mailer: Gnus/5.13 (Oort 5.13) Emacs/23.0.60.1 (x86_64-pc-linux-gnu) X-Mail-Morse: .-- .- .... .--- .- ...- .- .--.-. --. -- .- .. .-.. .-.-.- -.-. --- -- X-Attribution: =?utf-8?B?4KSG4KS24KWA4KS3?= Date: Tue, 09 Dec 2008 22:36:18 +0530 In-Reply-To: <20081209143052.GA29817@hades.panopticon> (Dmitry Marakasov's message of "Tue, 9 Dec 2008 17:30:52 +0300") Message-ID: <873agxjn1x.fsf@chateau.d.lf> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJ1BMVEWpqal/f39tbW1jY2Md HR2goKCenp6UlJROTk7////9/f35+fnT09ORJdieAAACVklEQVQ4jXXUP2vbQBQA8AvUTkgz5OzY Z0iGWhpS6BSrkECn0mvx0MEJ6AjtYrfoBCVDlD8naJYmNlRfwZq8+mkKlIZaGpJSYmP7Q/XkJDrJ Td8i/H68u3vHPaPufwLdf32AMA4A6GcAgvAamY1pOJiDIFqicTwLswDhfr3uxfFtkAY/GFHPMwzD 8zpnACmIOnE6js7rQb+v4NJrG9od0C+QgpHMy5jBewV+UDSMWiw1Y4fWfyV7+NGFzDsYa3pth9LJ Q4XvXxFHcJRvHOmygn5NAEabnDcQQguarnfoiwSCJ99jmKKcphsZONmWsDK9Ro7cvZOCtQdg8nje egLhc2LNlkLmsezzTFUUy5w18ocox/f0LaLgJy0zO75zk+9pp85GAj36xjqhdI0y3tq2m4dqqcWX zQWBTz8L1irvolXV4J+3q7eCDgVnttjNq6X8H+9KOZsuNk1uCzx8pSp+E9HImfJOTLdcGqo+YKnG EIovizkEn48V7BO+ch2DXcD4ENSpWiU+q8hjjbgTBZCXnZtyj0Ws4Q1Q0B2WXFtYZo65Bbyeeldw RS6qFueM80LlLA29YlVwGRYvFD+kwI/0O+A2PlpOP9GwslUVciHuYGechuBTp922YiDZCrghTknm XSyOM+D3aoRZlo0Jb42zY7DN4p2x4AeZ+QAYutx1sHwTHzMT5cMNduQ9yW3GczN4KZ86kb0c9O8T yXDeFqpl2fryPEAYGXIlezAPXYh2NgVr/gvdoHIuDwuPwOhcWE8f8mmICq41eATkn8x0kuRTIKcB wE9+/QUtiiAnYcaN7wAAAABJRU5ErkJggg== MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Cc: FreeBSD Ports Mailing List Subject: Re: [PROPOSAL] Ports using SCM repositories as source instead of distfiles 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: Tue, 09 Dec 2008 17:04:21 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Dmitry Marakasov writes: > * Ashish Shukla आशीष शुक्ल (wahjava.ml@gmail.com) wrote: >> I'm to proposing an enhancement to existing FreeBSD ports system. I >> think it'll be great if ports can use SCM (source code management) >> repositories like CVS, Subversion, Git, etc. as their sources instead of >> distfiles. Following are some of the {dis,}advantages of this approach: > This was discussed before. The summary: this won't work with ports. > Reasons: > - No way to track port updates. > - No way to save distfile. Source will be redownloaded on every rebuild. > - Security. No one can guarantee that malicious source won't be cheched > into the repository at some random time. Fixed versions can be at > least minimally checked and it is possible to not update the port to > new version if it contains problems and/or tell users to not install > version XXX. Impossible for SCM-based ports. >> * ATM, development versions of ports are packaged as snapshots, and >> maintainer has to keep updating ports snapshots. And sometimes, >> it is not possible for maintainer (due to lack of time and other >> issues) to update snapshots timely. So going proposed way can ease the >> work for them, and beneficial for users who are interested in latest >> bits. > - _Much_ more (instead of less) work for maintainer, as he won't be able > to test the port before committing it and will have to deal with all > the problems post factum, under extra pressure. > - Actually, any SCM-based port will become broken rather soon than > later with no ability to prevent it. > The port uses patches? Due to mutable source it'll become broken. > Any structural change upstream? Port broken. Changed build system? > Broken. Changed paths? Broken. Changed depends? Broken. Changed > options/configure args? Broken. Etc. These are the problems already expected with this but the only suggestion is to have PRs filed if anything breaks during compilation and investigate what caused it. >> * I've not played (or worked) with dynamic packaging lists on FreeBSD, >> so I'm not sure if it is possible to properly track all installed >> files dynamically, e.g. if a new commit in the upstream causes 3 new >> files to be installed, then is it possible for FreeBSD ports >> management system to include those 3 files also in the packing list, >> in the next installation of the port, hmm...? > - Generic dynamic plist generation is impossible unless the port > is installed into some clean chrooted environemnt (for example, > using DESTDIR). The latter, however takes extra space and time, > as you need the whole system and all dependent packages installed > there as well. Simply building the port will become more more like > producing package in a tinderbox: > - unpack the system image > - mount all required filesystems - devfs, ports, distfiles, packages > - install all required packages > - take list of all files in the chroot > - chroot and install the port > - take list of all files in the chroot, compare with previous one and > make a plist out of it > - umount and remove everything > - now you have package and may install in normally So, this is the main reason which prevents this :( . >> * As far as PR related to such ports are concerned I think one should >> directly submit them to the upstream rather than maintainer, unless >> that PR has anything to do with its packaging, in which case it should >> be submitted to FreeBSD PR system. > Sometimes it's hard to tell whether the problem is FreeBSD-specific. > Also, upstream is unlikely to have FreeBSD box for testing, so again > it'll be more work for maintainer. True, so either have all PRs should be submitted to FreeBSD PR system, where maintainer will decide if its porting issue or upstream related issue. So with all the problems you mentioned above, I guess, I'll take my proposal back :) . Thanks for your comments. -- Ashish Shukla --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkk+pYoACgkQHy+EEHYuXnQtKgCgwRddTLuIzHjclDkHNxLr45mA 7igAnA+8zM+B+r7nvZi+Tzk0+6cWi/NB =LERf -----END PGP SIGNATURE----- --=-=-=--