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, you
On 2022-04-09 03:25, Kyle Evans wrote:
FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
where a backup is created for every file patched.
I'd like to test the waters on switching this to the GNU behavior,
which feels a whole lot more reasonable. Notably, they'll only create
b
Hello folks,
I'm fairly new to the porting game so please bear with me.
A few months ago, I created my first port: sysutils/cpufetch
Back then, I was only testing this on amd64 so ONLY_FOR_ARCHS was set to amd64.
In the meantime, I've spun up some i386 VMs (both FreeBSD 13 and 14) as
upstream ad
On Mon, Apr 11, 2022 at 7:24 PM wrote:
>
> Hello folks,
>
> I'm fairly new to the porting game so please bear with me.
>
> A few months ago, I created my first port: sysutils/cpufetch
> Back then, I was only testing this on amd64 so ONLY_FOR_ARCHS was set to
> amd64.
> In the meantime, I've spun
On 11 Apr 2022, at 19:53, Fernando Apesteguía wrote:
>
> On Mon, Apr 11, 2022 at 7:24 PM wrote:
...
>> gmake[1]: Entering directory
>> '/wrkdirs/usr/ports/sysutils/cpufetch/work/cpufetch-1.00'
>> Makefile:38: Unsupported arch detected: i386. See
>> https://github.com/Dr-Noob/cpufetch#1-support
Oooh! This is so obvious it almost hurts...
So basically what happened is that upstream's v1.00 release that the port is
building didn't yet support i386. Meanwhile, I was able to compile
successfully on my VMs because I was using the main/master branch which does
support i386.
I hope we can just
On Mon, Apr 11, 2022 at 8:04 PM wrote:
>
> Oooh! This is so obvious it almost hurts...
> So basically what happened is that upstream's v1.00 release that the port is
> building didn't yet support i386. Meanwhile, I was able to compile
> successfully on my VMs because I was using the main/master b
> I would cherry pick the patch with PATCHFILES:
> https://docs.freebsd.org/en/books/porters-handbook/book/#makefile-distfiles
>
> +PATCH_SITES= https://github.com/Dr-Noob/cpufetch/commit/
> +PATCHFILES= 0db9f1f5c26e57a6383f4609c5605ed5d3d41fd1.patch:-p1
>
> I already have the change ready to push
On Mon, Apr 11, 2022 at 8:14 PM wrote:
>
> > I would cherry pick the patch with PATCHFILES:
> > https://docs.freebsd.org/en/books/porters-handbook/book/#makefile-distfiles
> >
> > +PATCH_SITES= https://github.com/Dr-Noob/cpufetch/commit/
> > +PATCHFILES= 0db9f1f5c26e57a6383f4609c5605ed5d3d41fd1.pa
I'd have a follow up question based on your commit: What's the reason for not
increasing PORTVERSION after modifying the port?
~ Joel
--- Original Message ---
On Monday, April 11th, 2022 at 20:18, Fernando Apesteguía
wrote:
> On Mon, Apr 11, 2022 at 8:14 PM jbo@insane.engineer wrote:
[Copying -ports; the issue could be interesting to others]
On Monday, 11 April 2022 at 0:22:23 -0700, Mark Millard wrote:
> From: Greg 'groggy' Lehey
> Date: Mon, 11 Apr 2022 09:04:43 +1000 :
>
>> I've checked both IPv4 sites, and
>> http://pkg.FreeBSD.org/FreeBSD:14:amd64/ only contains a "late
On 2022-Apr-11, at 16:46, Greg 'groggy' Lehey wrote:
> [Copying -ports; the issue could be interesting to others]
>
> On Monday, 11 April 2022 at 0:22:23 -0700, Mark Millard wrote:
>> From: Greg 'groggy' Lehey
>> Date: Mon, 11 Apr 2022 09:04:43 +1000 :
>>
>>> I've checked both IPv4 sites, and
On 2022-Apr-11, at 17:50, Mark Millard wrote:
> On 2022-Apr-11, at 16:46, Greg 'groggy' Lehey wrote:
>
>> [Copying -ports; the issue could be interesting to others]
>>
>> On Monday, 11 April 2022 at 0:22:23 -0700, Mark Millard wrote:
>>> From: Greg 'groggy' Lehey
>>> Date: Mon, 11 Apr 2022 0
On Mon, Apr 11, 2022 at 10:12 PM wrote:
>
> I'd have a follow up question based on your commit: What's the reason for not
> increasing PORTVERSION after modifying the port?
That the resultant package will not change and that the port becomes
buildable where it wasn't previously.
https://docs.fr
14 matches
Mail list logo
