Date: Sat, 7 Nov 2015 13:13:14 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: =?UTF-8?Q?Torsten_Z=C3=BChlsdorff?= <mailinglists@toco-domains.de> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, ports <freebsd-ports@freebsd.org> Subject: Re: Call for Help: need script for patching ports tree, building with poudriere Message-ID: <CAG=rPVfvzYmf84TULoPdrXNp=-7qkke=9jX-biOX5evcus0cnA@mail.gmail.com> In-Reply-To: <563E34C6.9010500@toco-domains.de> References: <CAG=rPVcOb4g9DD08c7vAsor8UMf3GnckAJ2wkO37p8Ao3G2GwA@mail.gmail.com> <563E34C6.9010500@toco-domains.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 7, 2015 at 9:28 AM, Torsten Z=C3=BChlsdorff < mailinglists@toco-domains.de> wrote: > > > It: > - assumes that patches are generated against /usr/ports (which makes > applying much easier) > - apply the patches > - get the ports affected by the diff with svn diff > - runs portlint > - runs poudriere for many versions... > - reset every change made to the portstree > > That flow of steps is very close to what I need. The scripts in http://github.com/freebsd/freebsd-ci are mostly shell or Python, but I'm flexible, as long as the scripts run under FreeBSD. I think you mentioned one problem about starting something, and then running out of time to finish working on it. This problem is very common. :( Hopefully if we have multiple people working on something and collaborating, we can get something going that many people can maintain and enhance in future. I would say go ahead and provide your script via GitHub pull request, unless you want to clean it up a little before providing it. Thanks. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVfvzYmf84TULoPdrXNp=-7qkke=9jX-biOX5evcus0cnA>