From owner-freebsd-questions@freebsd.org Mon Jan 11 09:16:30 2021 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 8F1284D1AE9 for ; Mon, 11 Jan 2021 09:16:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) (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 4DDp3x4nMMz4vPB for ; Mon, 11 Jan 2021 09:16:29 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.222.8.191]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPA (Nemesis) id 1N9MYu-1ju0yb1AJw-015J17; Mon, 11 Jan 2021 10:16:25 +0100 Date: Mon, 11 Jan 2021 10:16:24 +0100 From: Polytropon To: "Thomas Mueller" Cc: freebsd-questions@freebsd.org Subject: Re: github ports Message-Id: <20210111101624.1c7b97e3.freebsd@edvax.de> In-Reply-To: <202101110905.10B95CDu001945@r56.edvax.de> References: <20210110133605.6538dfd5@dismail.de> <202101110905.10B95CDu001945@r56.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:U93LBaXe3cMg81MKQqLMcORtjh3tWLj52BZZm07rNdOTWiNoBDq fFB7XuE7z+enZZo+FlXO6ddEa4gpYJZ2+yMJ6XNbq3ubUgf3VvxIOawbvUt4dt0D8gDZsPg uoWDmtTm24LwdxzjEkJm/VNRkA8cpmSXtrcuocsjKLzvGLzJjNYfLhJXQIEAUp25Yec1SIR QLMQFM5q1xP7F/a8rwrmg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:4iMjuVUaM5A=:ddkIYW8h3b7GEzyWbk7s2M hiwIv5pouxdBfayJ5P9lcubTPtwXUil+YELBWFgYfGM7Q4cE1acSF0k8wCgbCOYl3mqy/WaAD xcbMoXIw257DdKv5ETM4VYKNtMiyqL19ldG1oPfnnEVKSpkf4AdJgjNJsyT1/KbyE32IOfK/p FfDSSllTwVFp9zqlZAReziTiFThYDGPOOnPIO2L6lGtHqbxJtHNlsDtEyhho7vsw8LJX0nUD2 xX+uzfvFWRMMryspPrVwoloVxkRNqVUqX5X+RQNtD0kQhWe8198LB4a1ElosqepoP0/9V00t/ FZ9h9kknNqLrlXzXi2yKuD2cTciFPSj8l61movtXZUh+FsKolmGK5b1gKL4Stk8Hpb/J+bt1O 32939fl16DEbxN//OyYyV2xNzmk1I1mpTn1BvhN0BMD40uuBPPTnhkBAPUhAp X-Rspamd-Queue-Id: 4DDp3x4nMMz4vPB 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.135) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [1.27 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[twc.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[94.222.8.191:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.87)[0.865]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.135:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_VERYGOOD(0.00)[212.227.126.135:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2021 09:16:30 -0000 > As I remember, FreeBSD used csup for src and doc trees, also ports > tree, but switched to svn in 2012 because of a security breach with > csup. Initially, you had to install cvs (the whole package) or cvsup-without-gui. Later on, a CVS client written in C called csup was made part of the OS. With the transition to Subversion, the same happened: at first you needed to install SVN, later on a "small" client called svnlite was added to the OS. If I understood the planning correctly, a similar approach is intended for Git, i. e., a Git client will become part of the OS so you can obtain the sources without having to install the whole Git software package and its many dependencies. > I used portsnap before that for the ports tree, but then > switched to svn, since I was tracking src and doc trees and > was motivated by one-stop shopping. Additionally, the "make update" mechanisms for source-based updating work best with CVS / SVN / Git, especially if you just want to obtain some little delta of a few days. The scope of Git and portsnap, from a user's perspective, is so different that it would be nice to have two distinct tools (except Git gains the capabilities of portsnap). Just compare the "whole ports tree" method of portsnap with obtaining the "whole src tree" method of freebsd-update, having the "src" distribution enabled. > I suspect portsnap will no longer be workable. That is not implied, but could be possible. My understanding is that it's technically possible to create a snapshot (the "snap" part of the portsnap name) from a Git-based ports tree and then distribute that as a binary package. Of course the mechanisms to do so would have to be adapted from SVN to Git... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...