oybox-0.8.4.diff
And then create a PR and upload the diff file.
You don’t have to specify the category/port for 'svn diff', but it makes it go
faster as it won’t have to scan for changes in any other places than what you
specify.
Hope this cleared it up,
Vidar Karlsen
__
if you have to make
changes to the upstream code itself in order for it to work on FreeBSD. I
personally do that in the port’s ‘work’ dir and create the patches with ‘make
makepatch’, and there I need to create .orig files (cp file.c file.c.orig
before making changes).
Hope this helps,
On 4/17/20 7:24 AM, Hiroki Tagato wrote:
Can you apply a patch at https://github.com/nodejs/node/pull/29541 and
try to build again? If it goes well, I will update the port to include
the patch.
Thanks,
Hiroki
It passes the configure phase with that change to the regex, but it
fails later.
On 4/16/20 6:49 AM, Dimitry Andric wrote:
On 15 Apr 2020, at 22:14, Vidar Karlsen wrote:
BUILDING.md says it needs llvm 3.3 or higher, and I have clang 10.0.0. Is this
simply a version check gone wrong in node?
Very likely. When FreeBSD went to version 10, lots of sloppy configure
scripts
NG.md says it needs llvm 3.3 or higher, and I have clang 10.0.0.
Is this simply a version check gone wrong in node?
Cc-ing to ports list.
--
Best regards,
Vidar Karlsen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
from Norway too. wget works.
—
Vidar Karlsen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
connected to a random MUD server (there goes the weekend, I guess)
and it works.
--
Vidar Karlsen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> On 18 Mar 2018, at 22:33, Serpent7776 wrote:
>
> Just note your url is missing dash, here's corrected:
> https://github.com/vkarlsen/freebsd-ports/tree/master/deskutils/qlipper
Thanks, I must have fat-fingered it, “freebsd-ports” with the dash is indeed
correct.
d it a bit and bumped it to the latest released version 5.1.1.
It builds (poudriere testport on 11.1 and 10.4) and runs (tested on 11.1).
--
Vidar Karlsen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> On 13 Oct 2017, at 20:06, Jos Chrispijn wrote:
>
>
> Op 12-10-2017 om 20:19 schreef Vidar Karlsen:
>> I usually get that exact error when I run pkg from a directory that no
>> longer exists. In my case, this typically happens because I’m sitting in a
>> port d
> On 12 Oct 2017, at 19:50, Jos Chrispijn wrote:
>
> Op 12-10-2017 om 7:39 schreef Vidar Karlsen:
>> Also check if your current work dir has been deleted,
> Do you mean my BSD workdir like /temp or do you refer to the workdir that is
> used during the portupdate?
>
eck if your current work dir has been deleted, say, as a consequence of
running portsnap update for example. That can also trigger this error:
vidar@cube ~% mkdir -p one/two
vidar@cube ~% cd one/two
vidar@cube ~/one/two% rm -rf ~/one
vidar@cube ~/one/two% pkg info
pkg: sqlite erro
containing info about where to look for usage info.
>>
> The only documentation is the README.md file. You might drop the
> maintainer, vi...@karlsen.tech, a note suggesting that it be installed into
> /usr/local/share/doc/foid-zone-tools and a line to that effect be added to
> pk
13 matches
Mail list logo
