Re: WIP: Major UPDATE to py-flask and its dependencies | Help needed

2022-03-10 Thread f.holop
Stuart Henderson - Thu, 10 March 2022 at 12:54:12 > The difference is that other ports of standalone software are using > flask. (onionshare, puppetboard etc) yes, and there were no django based apps in ports... system packages are fine until all software runs on the same pinned flask version.

Re: WIP: Major UPDATE to py-flask and its dependencies | Help needed

2022-03-10 Thread f.holop
Ricardo - Sat, 26 February 2022 at 02:24:20 > I just noticed that our version of www/py-flask and its dependencies > are ancient. Current flask version is from almost 4 years ago, even > though the project released 2.0.0 a couple of months ago and stills > active maintain it. i'll say the same

Re: curl with libidn

2020-06-07 Thread f.holop
Stuart Henderson - Fri, 05 June 2020 at 00:03:04 > Adding it would add more code to something that is quite a common > dependency. Maybe it's useful enough to be worth it (being from a > country with mostly 7-bit charset I don't get much of a vote in this ;) > but along with the upside of support

curl with libidn

2020-06-04 Thread f.holop
hi, atm curl is unable to open non ascii domains. is there a reason why it's not compiled with libidn? (same goes for lynx) -f --

NEW: hyperfine: command line benchmarking tool

2020-05-17 Thread f.holop
hi, $ cat DESCR Command-line benchmarking tool. Features: - Statistical analysis across multiple runs. - Support for arbitrary shell commands. - Constant feedback about the benchmark progress and current estimates. - Warmup runs can be executed before the actual benchmark. - Cache-clearing

NEW: hyperfine: command line benchmarking tool

2020-04-27 Thread f.holop
hi, i know the ports tree is close to lockdown, but i'll just post this here so it can be picked up whenever it can be picked up again. thanks for all the help and patience while i struggled through the ports version of `cargo install ...` :} this tool can help nicely to test the performance

Re: `[modcargo] moving crates` fails

2020-04-27 Thread f.holop
Sebastien Marie - Sun, 26 April 2020 at 19:48:07 > On Sun, Apr 26, 2020 at 05:59:01PM +0200, f.holop wrote: > > Stuart Henderson - Sun, 26 April 2020 at 16:30:32 > > > Don't list the main distfile (i.e. the port itself) in MODCARGO_CRATES. > > > > yes of course, d

Re: `[modcargo] moving crates` fails

2020-04-26 Thread f.holop
Stuart Henderson - Sun, 26 April 2020 at 16:30:32 > Don't list the main distfile (i.e. the port itself) in MODCARGO_CRATES. this way the source for the actual port never gets extracted. $ make extract +++ Sun Apr 26 18:35:43 CEST 2020 ===> Checking files for hyperfine-1.9.0

Re: explanation of FETCH_PACKAGES in ports(7)

2020-04-26 Thread f.holop
Stuart Henderson - Sun, 26 April 2020 at 17:11:21 > > thank you for the explanations. i am afraid none of this comes across > > really from the man page as it is formulated now. but i am not a native > > speaker, true. > > it doesn't come across at all. diffs welcome ;) do you really want

Re: explanation of FETCH_PACKAGES in ports(7)

2020-04-26 Thread f.holop
Stuart Henderson - Sun, 26 April 2020 at 16:29:30 > On 2020/04/26 16:42, f.holop wrote: > > hi, > > > > i am having difficulties understanding this sentence, could someone > > help me out? > > > > > > FETCH_PACKAGES > >

Re: `[modcargo] moving crates` fails

2020-04-26 Thread f.holop
Stuart Henderson - Sun, 26 April 2020 at 16:30:32 > Don't list the main distfile (i.e. the port itself) in MODCARGO_CRATES. yes of course, don't touch yourself while time travelling :} now i get this: ===> Extracting for hyperfine-1.9.0 [modcargo] moving crates to

`[modcargo] moving crates` fails

2020-04-26 Thread f.holop
hi, i cannot seem to build a fairly simple rust port. all goes fine until moving the crates: ===> Extracting for hyperfine-1.9.0 [modcargo] moving crates to /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates mv: rename /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0

explanation of FETCH_PACKAGES in ports(7)

2020-04-26 Thread f.holop
hi, i am having difficulties understanding this sentence, could someone help me out? FETCH_PACKAGES If set, try to use as options to pkg_add(1) to install the missing packages from PKG_PATH. For instance: make FETCH_PACKAGES=

rust porting question (was: Re: make extract woes (rust))

2020-04-20 Thread f.holop
another day, another rust porting question :} what can i do when the crate name is different from GH_PROJECT? https://github.com/sharkdp/fd/blob/master/Cargo.toml name = "fd-find" repository = "https://github.com/sharkdp/fd; -f --

Re: make extract woes (rust)

2020-04-20 Thread f.holop
Stuart Henderson - Mon, 20 April 2020 at 00:28:29 > Remove the old MODCARGO_CRATES entries, run "make modcargo-gen-crates" > and include the newly generated list in the port Makefile. i did a `make makesum` here... > Then "make modcargo-gen-crates-licenses" and replace the list in the > Makefile

Re: make extract woes (rust)

2020-04-20 Thread f.holop
Stuart Henderson - Mon, 20 April 2020 at 00:28:29 > Remove the old MODCARGO_CRATES entries, run "make modcargo-gen-crates" > and include the newly generated list in the port Makefile. should i do something with the duplicates in the list? MODCARGO_CRATES += rand_core 0.3.1

Re: The great find(1) cleanup

2020-04-20 Thread f.holop
Christian Weisgerber - Thu, 19 March 2020 at 22:38:30 > Make use of "find -exec {} +" (which is POSIX) and "find -delete" > (which is not) throughout the ports Makefiles. > > Specifically: > > * Replace find|xargs with find -exec {} + > find|xargs is an outdated construct. The -exec {} +

Re: UPDATE: py-django

2020-04-20 Thread f.holop
Jasper Lievisse Adriaanse - Mon, 20 April 2020 at 09:18:23 > Hi, > > Without a maintainer it seems our django ports were lagging behind a bit. > Here's > an update to the latest versions of the branches we were tracking. > Both of them contain a number of security fixes. > > As the 1.11 LTS

Re: make extract woes (rust)

2020-04-20 Thread f.holop
Stuart Henderson - Mon, 20 April 2020 at 09:45:19 > So for some reason this file was fetched completely (this is the > normal name used when fetching until it's known that the file was > fetched) but wasn't renamed, and the left-over file is getting in the > way. my first build was indeed

Re: make extract woes (rust)

2020-04-20 Thread f.holop
Stuart Henderson - Mon, 20 April 2020 at 00:28:29 > It's trying to continue fetching (ftp -C) but the range request is > rejected because it's trying to fetch starting at the end of the file. > You'll see the same if you try to fetch it twice manually with ftp -C. > I guess it didn't get renamed

make extract woes (rust)

2020-04-19 Thread f.holop
hello, not my day. i am trying to put together my first rust port but failing miserably. i use ripgrep all the time. so i look at the port. i try to build it. it errors out right away: ~/src/ports/textproc/ripgrep$ make extract ===> Checking files for ripgrep-11.0.2p0

Re: github mirror

2020-04-19 Thread f.holop
Rafael Sadowski - Sun, 19 April 2020 at 21:32:21 > Use your own *global* gitignore. For more details see core.excludesFile: > https://git-scm.com/docs/gitignore thanks for tip. from all the local options though i wouldn't choose this one, as it could lead to hard to track down hair pulling

make update-patches woes (go lang)

2020-04-19 Thread f.holop
hello, i don't have experience with go ports and i cannot seem to have `make update-patches` work on this go project: ~/ports/sysutils/fzf$ make update-patches WRKDIST=/home/g/src/ports/pobj/fzf-0.21.1/fzf-0.21.1 does not exist *** Error 1 in /home/g/src/ports/sysutils/fzf

github mirror

2020-04-19 Thread f.holop
hello, i realize the github mirror comes as is, but i was wondering, if it would be possible to add a teeny tiny .gitignore with /distfiles/ /packages/ /plist/ /pobj/ (and possibly some others i have forgotten) -f -- second star to the right and straight on till morning.

Re: UPDATE sysutils/fzf

2020-04-19 Thread f.holop
I know i am a bit late to the party but here are my 2 cents: 1. without overriding FZF_DEFAULT_COMMAND, this port does not work from a shell that has no `set -o pipefail`: $ fzf [Command failed: set -o pipefail; command find -L . -mindepth 1 \( -path .. > i think that this is a bug and

Re: postgresql: libc collation issue, linking with ICU

2019-12-12 Thread f.holop
Jeremie Courreges-Anglas - Thu, 12 December 2019 at 11:35:51 > Can you actually use ICU as the default collation algorithm used by > a database? it's not totally straightforward but yes, on the schema level it's possible to override collation: macos=# CREATE TABLE t (n text COLLATE

Re: postgresql: libc collation issue, linking with ICU

2019-12-12 Thread f.holop
Landry Breuil - Thu, 12 December 2019 at 08:51:49 > On Thu, Dec 12, 2019 at 01:47:25AM +0100, Jeremie Courreges-Anglas wrote: > > > > +cc maintainer > > > > This has bugged me for some time, I think enabling ICU makes sense. > > Here's a wip diff. I fear it might cause issues with existing > >

Re: postgresql: libc collation issue, linking with ICU

2019-12-11 Thread f.holop
Ingo Schwarze - Wed, 11 December 2019 at 20:46:05 > Hi, > > Stuart Henderson wrote on Wed, Dec 11, 2019 at 07:19:16PM +: > > On 2019/12/11 19:57, f.holop wrote: > >> Ingo Schwarze - Wed, 11 December 2019 at 18:42:35 > > >>>> i have noticed that

Re: postgresql: libc collation issue, linking with ICU

2019-12-11 Thread f.holop
Ingo Schwarze - Wed, 11 December 2019 at 18:42:35 > > i have noticed that libc collation on OpenBSD is broken (also on macos) :( > > It is intentional that OpenBSD does not support collation for locales > other than "C" in libc, and i'm not aware of any developer who might > have plans to add it

Re: [NEW] fonts/firacode

2019-12-10 Thread f.holop
George Rosamond - Tue, 26 November 2019 at 10:36:09 > Wondering what others think about just having separate ports, the port > with ligatures as fonts/firacode and the regular font as fonts/fira, as > I submitted 20191123? They are in separate repos, so I don't see the > logic of arranging them

postgresql: libc collation issue, linking with ICU

2019-12-10 Thread f.holop
hello, i have noticed that libc collation on OpenBSD is broken (also on macos) :( openbsd=# select n from (values ('bernard'),('bérénice'),('béatrice'),('boris')) AS l(n) order by n collate "fr_FR" n -- bernard boris béatrice bérénice (4 rows) macos=# select n from (values