Date: Wed, 19 Jul 2017 23:10:40 +0000 From: Ben Woods <woodsb02@gmail.com> To: Athanasios Douitsis <aduitsis@cpan.org>, freebsd-ports@freebsd.org Subject: Re: github repo to port Message-ID: <CAOc73CAod1bK0s=s5m614m6Gma2vAAb90QOtQqUW=JDRG9B5qQ@mail.gmail.com> In-Reply-To: <CABT9mj9cjBQCx-JhWnwqpS3TPAvKSFeQ_nVGttUrdfMfhNQCVg@mail.gmail.com> References: <CABT9mj9cjBQCx-JhWnwqpS3TPAvKSFeQ_nVGttUrdfMfhNQCVg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Jul 2017 at 9:54 pm, Athanasios Douitsis <aduitsis@cpan.org> wrote: > Hello, > > Totally new to ports maintenance, please bear. > > Is there a way for a port to be semi-automatically updated from a github > repo as its source? > > I understand that a ports committer (which I am not) must always be present > in the process, just looking for the optimal way to handle maintenance. > > If this has been discussed before, my apologies. > > Many thanks, > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > Hi Athanasios, It's not automatic unfortunately. The process for updating a port (github or otherwise) is generally: 1. Change PORTVERSION in port Makefile 2. Run make makesum to update distfiles 3. Attempt port build to determine if it works, and if the files it installs has changed 4. Update pkg-plist with any changes to installed files (make makeplist). 5. Final testing/QA/QC and commit or submit bug report with patch if you are not a committee Regards, Ben -- -- From: Benjamin Woods woodsb02@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOc73CAod1bK0s=s5m614m6Gma2vAAb90QOtQqUW=JDRG9B5qQ>