Date: Sun, 19 Jan 2014 15:16:56 +0100 From: =?UTF-8?B?UGF3ZcWCIFRvbXVsaWs=?= <ptomulik@meil.pw.edu.pl> To: swills@FreeBSD.org Cc: ports@FreeBSD.org Subject: FreeBSD Port: puppet-3.4.2_2 Message-ID: <52DBDE58.4000600@meil.pw.edu.pl>
next in thread | raw e-mail | index | archive | help
Hi, I was working a little bit with puppet sources and wrote few modules for it. At some point I started wondering why do you patch certain freebsd-specific parts of puppet by your own instead of create pull request to upstream (https://github.com/puppetlabs/puppet). I mainly think about providers, for example: http://svnweb.freebsd.org/ports/head/sysutils/puppet/files/patch-demote_ports_provider?revision=300897&view=markup. Is there any reason for this? I have a master-slave setup, master is Debian, slave is FreeBSD, they have installed same version of puppet and I see difference in provider's code. It's quite strange IMHO. Perhaps you know that puppetlabs developers think about separating providers (and maybe few other pieces of code) from core, and they wish to turn them into independent modules: https://groups.google.com/forum/#!topic/puppet-dev/4y9ZvbbkKBs. Perhaps it's good point to have some of your patches applied to upstream project before they start this tiering process? I mean, the modules that are currently in puppet core may be subject to some pluginsync mechanism in the future and your patches may be then overwritten at runtime by the pluginsync mechanism. Regards! -- Pawel Tomulik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52DBDE58.4000600>