Re: How to fix/patch hardcoded values

Hello!, man(1) gitup only references: Files: ${PREFIX}/etc/gitup.conf Default location of the gitup configuration file. But yes, thats makes sense a per-user .config file, maybe in ~ or in ~/.config folder. Thanks! Chris escreveu no dia terça, 29/12/2020 à(s) 08:23: > On 2020-12-29 00:07, Ma

Re: How to fix/patch hardcoded values

Hello, I'm using: ${REINPLACE_CMD} 's,\./gitup.conf,${PREFIX}/etc/gitup.conf,' ${WRKSRC}/gitup.c I didn't know about that sintax with "%": ${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX}' ${WRKSRC}/githup.c Does it make any difference between the two expressions? Thanks Mathieu Arnold escreveu no

Re: How to fix/patch hardcoded values

On 2020-12-29 00:07, Mathieu Arnold wrote: On Sun, Dec 27, 2020 at 09:58:13PM +, Nuno Teixeira wrote: Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config in /usr/local/etc inst

Re: How to fix/patch hardcoded values

On Sun, Dec 27, 2020 at 09:58:13PM +, Nuno Teixeira wrote: > Hello I've just submited a new port net/gitup > and I used a > simple workaround to help program find its config in /usr/local/etc instead > of (hardcoded) ./ > > --- gitup.c

Re: How to fix/patch hardcoded values

In that case you might try an appropriate invocation of REINPLACE_CMD in post-patch. On 27/12/2020 22:58, Nuno Teixeira wrote: Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config

How to fix/patch hardcoded values

Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config in /usr/local/etc instead of (hardcoded) ./ --- gitup.c.orig 2020-12-27 21:16:22 UTC +++ gitup.c @@ -2030,7 +2030,7 @@ main(int ar