Re: getting PKGNAME from CONFLICTS

> On Aug 14, 2018, at 2:55 PM, Mark Millard via freebsd-ports > wrote: > > > Dan Langille dan at langille.org wrote on > Tue Aug 14 17:54:01 UTC 2018 : > >> . . . >> At https://dev.freshports.org/www/p5-CGI/ you can see: >> >> CONFLICTS: p5-CGI.pm-[1-3]* >> . . . >> To extract the PKGNAME

Re: getting PKGNAME from CONFLICTS

> On Aug 14, 2018, at 3:15 PM, Adam Weinberger wrote: > > On Tue, Aug 14, 2018 at 1:13 PM Adam Weinberger wrote: >> >> On Tue, Aug 14, 2018 at 11:54 AM Dan Langille wrote: >>> >>> I am in the process of adding FreshPorts support for CONFLICTS[1]. >>> >>> I reference www/p5-CGI only because

Re: getting PKGNAME from CONFLICTS

On Tue, Aug 14, 2018 at 1:13 PM Adam Weinberger wrote: > > On Tue, Aug 14, 2018 at 11:54 AM Dan Langille wrote: > > > > I am in the process of adding FreshPorts support for CONFLICTS[1]. > > > > I reference www/p5-CGI only because it had a recent commit and it contains > > a CONFLICTS

Re: getting PKGNAME from CONFLICTS

On Tue, Aug 14, 2018 at 11:54 AM Dan Langille wrote: > > I am in the process of adding FreshPorts support for CONFLICTS[1]. > > I reference www/p5-CGI only because it had a recent commit and it contains a > CONFLICTS directive. > > At https://dev.freshports.org/www/p5-CGI/ you can see: > >

Re: getting PKGNAME from CONFLICTS

Dan Langille dan at langille.org wrote on Tue Aug 14 17:54:01 UTC 2018 : > . . . > At https://dev.freshports.org/www/p5-CGI/ you can see: > > CONFLICTS: p5-CGI.pm-[1-3]* > . . . > To extract the PKGNAME values from the CONFLICTS I will need to remove > everything after the trailing dash.

getting PKGNAME from CONFLICTS

I am in the process of adding FreshPorts support for CONFLICTS[1]. I reference www/p5-CGI only because it had a recent commit and it contains a CONFLICTS directive. At https://dev.freshports.org/www/p5-CGI/ you can see: CONFLICTS: p5-CGI.pm-[1-3]* My goal is to allow a link to the search

Re: workflow question: how do you maintain the port in sync with upstream?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 14 Aug 2018 17:33:38 +0200 Mathieu Arnold wrote: > On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote: > > This one is fairly straight forward, you can simply replace that > > string with a regex command; > > This is an

Re: workflow question: how do you maintain the port in sync with upstream?

On Tue, Aug 14, 2018 at 11:33 PM Mathieu Arnold wrote: > On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote: > > This one is fairly straight forward, you can simply replace that string > > with a regex command; > > This is an example of running a replace command for strings after

Re: workflow question: how do you maintain the port in sync with upstream?

On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote: > This one is fairly straight forward, you can simply replace that string > with a regex command; > This is an example of running a replace command for strings after the patch > phase of the build; > > post-patch: >

Re: workflow question: how do you maintain the port in sync with upstream?

On Tue, Aug 14, 2018 at 10:23 PM Helen Koike wrote: > > > On 08/14/2018 12:05 AM, Adam Weinberger wrote: > > On Mon, Aug 13, 2018 at 4:28 PM Helen Koike > wrote: > >> > >> Hello, > >> > >> I am new to the community, I am maintaining two packages and I would > >> like to check with you if there

Re: workflow question: how do you maintain the port in sync with upstream?

On Tue, Aug 14, 2018 at 8:56 PM Helen Koike wrote: > > > On 08/13/2018 09:50 PM, blubee blubeeme wrote: > > > > > > On Tue, Aug 14, 2018, 08:26 Helen Koike > > wrote: > > > > > > > > On 08/13/2018 08:00 PM, blubee blubeeme wrote: > > > > > > > >

Re: workflow question: how do you maintain the port in sync with upstream?

On Tue, Aug 14, 2018 at 11:20:59AM -0300, Helen Koike wrote: > > > On 08/14/2018 12:05 AM, Adam Weinberger wrote: > > On Mon, Aug 13, 2018 at 4:28 PM Helen Koike > > wrote: > >> > >> Hello, > >> > >> I am new to the community, I am maintaining two packages and I would > >> like to check with

Re: workflow question: how do you maintain the port in sync with upstream?

On 08/14/2018 12:05 AM, Adam Weinberger wrote: > On Mon, Aug 13, 2018 at 4:28 PM Helen Koike wrote: >> >> Hello, >> >> I am new to the community, I am maintaining two packages and I would >> like to check with you if there is a better workflow to do this. >> >> The upstream project of the port

Re: workflow question: how do you maintain the port in sync with upstream?

On 08/13/2018 09:50 PM, blubee blubeeme wrote: > > > On Tue, Aug 14, 2018, 08:26 Helen Koike > wrote: > > > > On 08/13/2018 08:00 PM, blubee blubeeme wrote: > > > > > > On Tue, Aug 14, 2018, 06:30 Helen Koike

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,

net-mgmt/docsis Update from 0.9.6 to 0.9.8

Hello FreeBSD Port Team The docsis Port moved from sf.net to github. Meanwhile they released the version 0.9.8 in october 2015 Can someone from the port-team update this port to reflect the changes? The current version of the port 0.9.6 is marked as IGNORE. I'm not