From owner-freebsd-ports@freebsd.org Mon Jun 27 18:06:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF168B841DC; Mon, 27 Jun 2016 18:06:03 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD58A21E9; Mon, 27 Jun 2016 18:06:03 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id j2so242521231vkg.2; Mon, 27 Jun 2016 11:06:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=uqi5feDamAw01JhhXlVDB/fqnUXxzz3v80juJnC86Is=; b=C2Z87HeK1CwPMY4UvkFV9mreLvdnm3Hsj5QWP0fwYJBzcBh691fHbTtKNHrOGdP6I6 81tR6xCKZ9Y7I9WS/orl/ea4WJemX2/iOW3YE46ExaW8JRFn8/kyb7h23FKR9JBhNSE0 8J41tw4PkxY1l369XgO5QcyfYFdE5CGbBAoGeVEfDBW/xgnqrXfEst+tAljcASUY+MJh WGKjPIL+JZ1xmPxtb/0gsPXxVejzwl628TOdXEe9030JzqtCt0lQhiu6Z3byPT2Iizf4 T8+Jn007s8oJGTrAUT+vgunZZiZA7PWojxYZM7opa/3s93ovBbFaaN+NUhdYa8V/Yj8s EerQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=uqi5feDamAw01JhhXlVDB/fqnUXxzz3v80juJnC86Is=; b=Oe6pkNbPsVd9TEkGAmIvWfMRcfgywac52ZLZXzWxpUuSJgFmxJedN0eBrBEVqDEPd/ khgHVUuKxtjqslnWS5LEGTU0sCTDyas6QUS3ZFXPd1O0AdZwQaG/B5NFD4L75njben4y Xk2N2zE+WoSs0QLQVmPTbgYi09v1EOj1RlBVtS1MoyXsLnESH4RWrBuIHQvsQg/UrO/K Smft92BOVJmRGsx+h8y4KuO9CllAuuOVL5vonz+BoPsqR69Hww8JDpsA3QBPJJ/3iIjp 9QiGo7xZXAOaOBCuZQM93lSFM04OIPEVsu8bhNXBn2cyYbKXBt365EzLGPoqZP1kr6HC caZg== X-Gm-Message-State: ALyK8tIyApKjd8rwhAyhNTrWaWC6lPeVFneqkit8xAL6JzIm0x1xNXjPcydoalQXiRONCDJk6SJNisx5pqgsoQ== X-Received: by 10.31.210.133 with SMTP id j127mr8868988vkg.143.1467050762672; Mon, 27 Jun 2016 11:06:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.54.196 with HTTP; Mon, 27 Jun 2016 11:06:02 -0700 (PDT) From: Russell Haley Date: Mon, 27 Jun 2016 11:06:02 -0700 Message-ID: Subject: Maintaining mono/.net To: freebsd-ports@freebsd.org Cc: Freebsd-mono Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 18:06:04 -0000 Hello Ports Team, A couple of us on the freebsd-mono@ mailing list are having a discussion on how best to maintain the mono ports/.net ports. One of the things that has come up is maintaining the patches for "all this stuff". The current paradigm in FreeBSD as I understand it is to use the files directory and apply the patches to the port via svn/ports tree. However, with the ubiquity of GitHub in opensource, it now seems to be feesable to simply create a Github accound to maintain a bunch of forked repositories (which is essentially a patched git repository!). This makes it easier to create and apply patches and gives us the natural path to push things back upstream. In the end, we would just pull from the FreeBSD specific repository, which is no different than, say, pulling from the mono project directly. This email is a request for response from anyone on the ports team (or FreeBSD general) to give some input as to the acceptability of this solution, as well as any "gotchas" we haven't thought of yet. Thanks in advance! Russ