Re: WIP: Major UPDATE to py-flask and its dependencies | Help needed
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. this is of course a python issue and every system has to deal with it. the current setup works basically as a matter of luck. whoever will want to have multiple applications on one machine sooner or later will have to switch to venv's, maybe not even because of flask, but something different. i dont mean to dismiss the work being done here, just as a python developer i recommend everyone to use venvs everywhere. i am not sure it's a system packager's job to provide packages for web apps that normally have other requirements as well (web server, etc). i'll shut up now. -f --
Re: WIP: Major UPDATE to py-flask and its dependencies | Help needed
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 for flask i said for django: there is very little benefit and a lot of work to keep these packages up to date when it's really best practices to use venv's with pinning. there is no benefit in having these as system packages. -f --
Re: curl with libidn
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 IDNs, there is a downside to > pulling in (historically a bit buggy) code to all ports using the > library. I agree, it is marginally useful... Is that margin worth it? In my case i needed this to troubleshoot quickly an RSS feed on such a domain. It would be nice to have a curl and curl-idn package without me having to hand roll one. But then where is the limit for a "swiss army knife" tool? Some linux distro packages come with everything curl can support compiled in down to gopher... -f --
curl with libidn
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
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 commands can be set up before each timing run. - Statistical outlier detection to detect interference from other programs and caching effects. - Export results to various formats: CSV, JSON, Markdown, AsciiDoc. - Parameterized benchmarks (e.g. vary the number of threads). - Cross-platform -f -- hyperfine.tgz Description: application/tar-gz
NEW: hyperfine: command line benchmarking tool
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 of the big find cleanup :] $ 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 commands can be set up before each timing run. - Statistical outlier detection to detect interference from other programs and caching effects. - Export results to various formats: CSV, JSON, Markdown, AsciiDoc. - Parameterized benchmarks (e.g. vary the number of threads). - Cross-platform -f -- hyperfine.tgz Description: application/tar-gz
Re: `[modcargo] moving crates` fails
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, don't touch yourself while time travelling :}
> >
> > now i get this:
> >
> > ===> 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
> > mkdir:
> > /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates: No
> > such file or directory
> >
>
> It could help if you look at some port using devel/cargo as example.
>
> you could see such lines in /usr/ports/textproc/ripgrep/Makefile:
>
> # as devel/cargo MODULES adds DISTFILES, GH_* didn't
> DISTFILES +=${DISTNAME}${EXTRACT_SUFX}
>
> the port itself needs to know what to download (DISTFILES) and have the list
> of
> crates used by it (MODCARGO_CRATES).
right.
yes, i saw that line in other ports. unfortunately the comment made
little sense to me as i dont have the rust porting experience of the
person who put it there.
is this always needed? only sometimes? which cases? why is it not
then in every cargo port?
is this something people trying to make rust ports will have to find
from mailing archives?
-f
--
Re: `[modcargo] moving crates` fails
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 `/home/f/src/ports/distfiles/cargo/ansi_term-0.11.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/approx-0.3.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/atty-0.2.13.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/autocfg-0.1.7.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/bitflags-1.2.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/bstr-0.2.8.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/byteorder-1.3.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/cfg-if-0.1.10.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/clap-2.33.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/clicolors-control-1.0.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/cloudabi-0.0.3.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/colored-1.9.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/console-0.9.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/csv-1.1.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/csv-core-0.1.6.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/encode_unicode-0.3.6.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/fuchsia-cprng-0.1.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/indicatif-0.13.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/itoa-0.4.4.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/kernel32-sys-0.2.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/lazy_static-1.4.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/libc-0.2.65.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/memchr-2.2.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-0.2.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-bigint-0.2.3.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-complex-0.2.3.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-integer-0.1.41.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-iter-0.1.39.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-rational-0.2.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/num-traits-0.2.10.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/number_prefix-0.3.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/proc-macro2-1.0.6.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/quote-1.0.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand-0.6.5.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_chacha-0.1.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_core-0.3.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_core-0.4.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_hc-0.1.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_isaac-0.1.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_jitter-0.1.4.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_os-0.1.3.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_pcg-0.1.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rand_xorshift-0.1.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rdrand-0.4.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/regex-1.3.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/regex-automata-0.1.8.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/regex-syntax-0.6.12.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/rust_decimal-1.0.3.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/ryu-1.0.2.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/serde-1.0.103.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/serde_derive-1.0.103.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/serde_json-1.0.42.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/statistical-1.0.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/strsim-0.8.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/syn-1.0.8.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/term_size-0.3.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/termios-0.3.1.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/textwrap-0.11.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/unicode-width-0.1.6.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/unicode-xid-0.2.0.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/winapi-0.2.8.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/winapi-0.3.8.tar.gz' is up to date. `/home/f/src/ports/distfiles/cargo/winapi-build-0.1.1.tar.gz' is up to date.
Re: explanation of FETCH_PACKAGES in ports(7)
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 diffs from someone who just asked others to explain it to him?...:] -f --
Re: explanation of FETCH_PACKAGES in ports(7)
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
> >If set, try to use as options to pkg_add(1) to install
> > the
> >missing packages from PKG_PATH. For instance:
> >
> > make FETCH_PACKAGES=
> >
> > -f
> > --
> >
>
> If set, even to an empty string) rather than building missing
> dependencies from source, pkg_add(1) will be called to install missing
> packages from PKGPATH.
>
> If not an empty string, it will be called as "pkg_add ${FETCH_PACKAGES}"
> which is useful in some niche cases.
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.
i roughly parse it as: "if you want to pass parameters to pkg_add, set
this to something." and then there is a (unexplained example) of
passing nothing...
while it's main function is really to stop `make build` going recursive
and all ballistic building every single needed thing not installed atm
as a package... (which is rarely what a single port job needs)
-f
--
Re: `[modcargo] moving crates` fails
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 /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates mkdir: /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates: No such file or directory -f --
`[modcargo] moving crates` fails
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 to /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates/hyperfine-1.9.0: Invalid argument is it trying to move itself inside `modcargo-crates` ? please find attached the WIP makefile. -f -- # $OpenBSD$ COMMENT = GH_ACCOUNT =sharkdp GH_PROJECT =hyperfine GH_TAGNAME =v1.9.0 CATEGORIES =sysutils # MIT/Apache-2.0 PERMIT_PACKAGE =Yes WANTLIB += c c++abi pthread MODULES = devel/cargo CONFIGURE_STYLE = cargo SEPARATE_BUILD =Yes MODCARGO_CRATES += ansi_term 0.11.0 MODCARGO_CRATES += approx 0.3.2 MODCARGO_CRATES += atty0.2.13 MODCARGO_CRATES += autocfg 0.1.7 MODCARGO_CRATES += bitflags1.2.1 MODCARGO_CRATES += bstr0.2.8 MODCARGO_CRATES += byteorder 1.3.2 MODCARGO_CRATES += cfg-if 0.1.10 MODCARGO_CRATES += clap2.33.0 MODCARGO_CRATES += clicolors-control 1.0.1 MODCARGO_CRATES += cloudabi0.0.3 MODCARGO_CRATES += colored 1.9.0 MODCARGO_CRATES += console 0.9.1 MODCARGO_CRATES += csv 1.1.1 MODCARGO_CRATES += csv-core0.1.6 MODCARGO_CRATES += encode_unicode 0.3.6 MODCARGO_CRATES += fuchsia-cprng 0.1.1 MODCARGO_CRATES += hyperfine 1.9.0 MODCARGO_CRATES += indicatif 0.13.0 MODCARGO_CRATES += itoa0.4.4 MODCARGO_CRATES += kernel32-sys0.2.2 MODCARGO_CRATES += lazy_static 1.4.0 MODCARGO_CRATES += libc0.2.65 MODCARGO_CRATES += memchr 2.2.1 MODCARGO_CRATES += num 0.2.0 MODCARGO_CRATES += num-bigint 0.2.3 MODCARGO_CRATES += num-complex 0.2.3 MODCARGO_CRATES += num-integer 0.1.41 MODCARGO_CRATES += num-iter0.1.39 MODCARGO_CRATES += num-rational0.2.2 MODCARGO_CRATES += num-traits 0.2.10 MODCARGO_CRATES += number_prefix 0.3.0 MODCARGO_CRATES += proc-macro2 1.0.6 MODCARGO_CRATES += quote 1.0.2 MODCARGO_CRATES += rand0.6.5 MODCARGO_CRATES += rand_chacha 0.1.1 MODCARGO_CRATES += rand_core 0.3.1 MODCARGO_CRATES += rand_core 0.4.2 MODCARGO_CRATES += rand_hc 0.1.0 MODCARGO_CRATES += rand_isaac 0.1.1 MODCARGO_CRATES += rand_jitter 0.1.4 MODCARGO_CRATES += rand_os 0.1.3 MODCARGO_CRATES += rand_pcg0.1.2 MODCARGO_CRATES += rand_xorshift 0.1.1 MODCARGO_CRATES += rdrand 0.4.0 MODCARGO_CRATES += regex 1.3.1 MODCARGO_CRATES += regex-automata 0.1.8 MODCARGO_CRATES += regex-syntax0.6.12 MODCARGO_CRATES += rust_decimal1.0.3 MODCARGO_CRATES += ryu 1.0.2 MODCARGO_CRATES += serde 1.0.103 MODCARGO_CRATES += serde_derive1.0.103 MODCARGO_CRATES += serde_json 1.0.42 MODCARGO_CRATES += statistical 1.0.0 MODCARGO_CRATES += strsim 0.8.0 MODCARGO_CRATES += syn 1.0.8 MODCARGO_CRATES += term_size 0.3.1 MODCARGO_CRATES += termios 0.3.1 MODCARGO_CRATES += textwrap0.11.0 MODCARGO_CRATES += unicode-width 0.1.6 MODCARGO_CRATES += unicode-xid 0.2.0 MODCARGO_CRATES += winapi 0.2.8 MODCARGO_CRATES += winapi 0.3.8 MODCARGO_CRATES += winapi-build0.1.1 MODCARGO_CRATES += winapi-i686-pc-windows-gnu 0.4.0 MODCARGO_CRATES += winapi-x86_64-pc-windows-gnu0.4.0 .include
explanation of FETCH_PACKAGES in ports(7)
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= -f --
rust porting question (was: Re: make extract woes (rust))
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)
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 with the new output which includes license information. i could not finish that step yet. portslogger output for `make`: +++ Tue Apr 21 00:02:36 CEST 2020 ===> Checking files for hyperfine-1.9.0 `/home/g/src/ports/distfiles/cargo/ansi_term-0.11.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/approx-0.3.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/atty-0.2.13.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/autocfg-0.1.7.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/bitflags-1.2.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/bstr-0.2.8.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/byteorder-1.3.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/cfg-if-0.1.10.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/clap-2.33.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/clicolors-control-1.0.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/cloudabi-0.0.3.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/colored-1.9.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/console-0.9.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/csv-1.1.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/csv-core-0.1.6.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/encode_unicode-0.3.6.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/fuchsia-cprng-0.1.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/hyperfine-1.9.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/indicatif-0.13.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/itoa-0.4.4.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/kernel32-sys-0.2.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/lazy_static-1.4.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/libc-0.2.65.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/memchr-2.2.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-0.2.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-bigint-0.2.3.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-complex-0.2.3.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-integer-0.1.41.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-iter-0.1.39.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-rational-0.2.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/num-traits-0.2.10.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/number_prefix-0.3.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/proc-macro2-1.0.6.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/quote-1.0.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand-0.6.5.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_chacha-0.1.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_core-0.3.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_core-0.4.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_hc-0.1.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_isaac-0.1.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_jitter-0.1.4.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_os-0.1.3.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_pcg-0.1.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rand_xorshift-0.1.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rdrand-0.4.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/regex-1.3.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/regex-automata-0.1.8.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/regex-syntax-0.6.12.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/rust_decimal-1.0.3.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/ryu-1.0.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/serde-1.0.103.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/serde_derive-1.0.103.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/serde_json-1.0.42.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/statistical-1.0.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/strsim-0.8.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/syn-1.0.8.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/term_size-0.3.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/termios-0.3.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/textwrap-0.11.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/unicode-width-0.1.6.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/unicode-xid-0.2.0.tar.gz' is up to date.
Re: make extract woes (rust)
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 MODCARGO_CRATES += rand_core 0.4.2 ... MODCARGO_CRATES += winapi 0.2.8 MODCARGO_CRATES += winapi 0.3.8 -f --
Re: The great find(1) cleanup
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 {} + invocation
> automatically avoids a number of corner cases (see xargs -0, -r).
i am late to this party too, but recently i did some research exactly
about the performance of xargs vs -exec vs -execdir and xargs is by far
the fatest on every platform except openbsd (i imagine becasue process
creation is heavier)
https://stackoverflow.com/a/60177893/4377759
(it was not testing -delete though)
> Also, since the exit status of the left-hand side of a pipe is
> ignored, find|xargs hides some problem.
it seems to me that `set -o pipefail` is becoming a thing in most shells
except openbsd's ksh... this is breaking the default command in fzf
(in another thread on this mailing list).
-f
--
Re: UPDATE: py-django
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 branch has gone out of support per April 1 this year, > we should move the 2.2 into the lts branch and add Django 3.0. > But perhaps this should be done after 6.7. > > OK for this update to plug a few holes? i might be a lone voice in this but i think a django port makes little sense. currently my work involves working with django daily and every django project will have a venv where all the deps will be installed, including django. system packages cannot help with this. another factor is the apps/libraries used with django which sometimes dictate the actual django version, for example some older dep might be not django 3 ready holding back the project to 2.*, etc. to be honest, this is mostly true for a lot of python packages/libs. this is one of the reasons i stopped updating/submitting new python packages to ports. i need them in the venv and ports cannot help me with that. this does not apply to applications proper of course, but django is framework, not a standalone application. -f -- it is easier to catch flies with honey than with vinegar.
Re: make extract woes (rust)
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 ctrl+c'd. however i did `make clean=dist` before starting the next build... is it expected that i need to clean up distfiles manually? > It's in port-modules(5) but it's more of a reference and expects some > existing knowledge really. yes, i had a look at it, it's a reference rather, and was not much help for me to get started. > > would be an idea to lower the barrier to entry by creating a couple of > > language specific makefile templates having workflow information > > and best practices? > > This would probably fit better in the ports faq than manpages. i was thinking more along the lines of infrastructure/templates/Makefile.template -f --
Re: make extract woes (rust)
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 from cfg-if-0.1.9.tar.gz.dist to > cfg-if-0.1.9.tar.gz maybe due to some permissions problem. > > ls -l distfiles/cargo/cfg-if-0.1.9.tar.gz* - anything look different > than other files? there are no permission problems as far as i see. but the filename is not good: $ ls -l distfiles/cargo/cfg-if-0.1.9.tar.gz* -rw-r--r-- 1 g wheel 7353 Apr 19 23:56 distfiles/cargo/cfg-if-0.1.9.tar.gz.part > > some other questions: > > > > where did this list of MODCARGO_CRATES come from? > > it's not the dep list in the toml file, so it's not > > like RUN_DEPENDS in python... is it _all_ the crates > > from the lock file? am i supposed to fill in the licenses > > for all of them manually? > > Remove the old MODCARGO_CRATES entries, run "make modcargo-gen-crates" > and include the newly generated list in the port Makefile. > > Then "make modcargo-gen-crates-licenses" and replace the list in the > Makefile with the new output which includes license information. > > If it now uses a new version of rust-libc newer than 0.2.63 that's ok, > if not then put MODCARGO_CRATES_UPDATE and MODCARGO_CRATES += libc 0.2.63 > back. thank you. is there documentation that i have missed, or is everyone simply expected to read the Makefile sources? would be an idea to lower the barrier to entry by creating a couple of language specific makefile templates having workflow information and best practices? i have python porting experience but big changes are coming/keep happening and keeping tabs on all these is unrealistic for me, hunting for drops of wisdom like this in mailing list archives... -f -- monotheism is a gift from the gods.
make extract woes (rust)
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 `/home/g/src/ports/distfiles/ripgrep-11.0.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/libc-0.2.63.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/aho-corasick-0.7.4.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/atty-0.2.13.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/base64-0.10.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/bitflags-1.1.0.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/bstr-0.2.6.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/bytecount-0.5.1.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/byteorder-1.3.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/c2-chacha-0.2.2.tar.gz' is up to date. `/home/g/src/ports/distfiles/cargo/cc-1.0.38.tar.gz' is up to date. >> Fetch https://crates.io/api/v1/crates/cfg-if/0.1.9/download ftp: File is already fully retrieved. >> Fetch https://ftp.openbsd.org/pub/OpenBSD/distfiles/cargo/cfg-if-0.1.9.tar.gz ftp: File is already fully retrieved. >> Fetch >> https://ftp.usa.openbsd.org/pub/OpenBSD/distfiles/cargo/cfg-if-0.1.9.tar.gz ftp: Error retrieving https://ftp.usa.openbsd.org/pub/OpenBSD/distfiles/cargo/cfg-if-0.1.9.tar.gz: 404 Not Found >> Fetch >> https://ftp.fr.openbsd.org/pub/OpenBSD/distfiles/cargo/cfg-if-0.1.9.tar.gz ftp: File is already fully retrieved. *** Error 1 in . (/home/g/src/ports/infrastructure/mk/bsd.port.mk:3136 '/home/g/src/ports/distfiles/cargo/cfg-if-0.1.9.tar.gz': @lock=cfg-if...) *** Error 2 in . (/home/g/src/ports/infrastructure/mk/bsd.port.mk:2447 '_internal-fetch': @cd /home/g/src/ports/textproc/ripgrep && PKGPATH=...) *** Error 2 in . (/home/g/src/ports/infrastructure/mk/bsd.port.mk:2652 '/home/g/src/ports/pobj/ripgrep-11.0.2/.extract_done': @cd/home/g/sr...) *** Error 2 in /home/g/src/ports/textproc/ripgrep (/home/g/src/ports/infrastructure/mk/bsd.port.mk:2573 'extract': @lock=ripgrep-11.0.2p0; ...) what does it mean "File is already fully retrieved." ? why is that a bad thing? some other questions: where did this list of MODCARGO_CRATES come from? it's not the dep list in the toml file, so it's not like RUN_DEPENDS in python... is it _all_ the crates from the lock file? am i supposed to fill in the licenses for all of them manually? -f -- foied vinom pipafo, cra carefo.
Re: github mirror
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 problems in some other projects.. -f -- if there's one thing i can't stand, it's intolerance.
make update-patches woes (go lang)
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 (/home/g/src/ports/infrastructure/mk/bsd.port.mk:2559 'update-patches': @toedit=`WRKDIST=/home...) ~/src/ports/sysutils/fzf$ make show=WRKSRC /home/g/src/ports/pobj/fzf-0.21.1/go/src/github.com/junegunn/fzf ~/src/ports/sysutils/fzf$ make ===> fzf-0.21.1 depends on: go-=1.13.9 -> go-1.13.9 ===> Verifying specs: c pthread ===> found c.96.0 pthread.26.1 ===> Checking files for fzf-0.21.1 `/home/g/src/ports/distfiles/fzf-0.21.1.tar.gz' is up to date. >> (SHA256) fzf-0.21.1.tar.gz: OK ===> Extracting for fzf-0.21.1 ===> Patching for fzf-0.21.1 ===> Compiler link: clang -> /usr/bin/clang ===> Compiler link: clang++ -> /usr/bin/clang++ ===> Compiler link: cc -> /usr/bin/cc ===> Compiler link: c++ -> /usr/bin/c++ ===> Generating configure for fzf-0.21.1 ===> Configuring for fzf-0.21.1 ===> Building for fzf-0.21.1 /usr/bin/env -i GOCACHE="/home/g/src/ports/pobj/fzf-0.21.1/go-cache" GOPATH="/home/g/src/ports/pobj/fzf-0.21.1/go:/usr/local/go-pkg" GO111MODULE=off GO386=387 GOPROXY=invalid://ports.should.not.fetch.at.buildtime/ PORTSDIR="/home/g/src/ports" LIBTOOL="/usr/bin/libtool" PATH='/home/g/src/ports/pobj/fzf-0.21.1/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11R6/bin' PREFIX='/usr/local' LOCALBASE='/usr/local' X11BASE='/usr/X11R6' CFLAGS='-O2 -pipe' TRUEPREFIX='/usr/local' DESTDIR='' HOME='/fzf-0.21.1_writes_to_HOME' PICFLAG="-fpic" BINGRP=bin BINOWN=root BINMODE=755 NONBINMODE=644 DIRMODE=755 INSTALL_COPY=-c INSTALL_STRIP= MANGRP=bin MANOWN=root MANMODE=644 BSD_INSTALL_PROGRAM="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -c -m 755" BSD_INSTALL_SCRIPT="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -c -m 755" BSD_INSTALL_DATA="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -c -m 644" BSD_INSTALL_MAN="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -c -m 644" BSD_INSTALL_PROGRAM_DIR="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -d -m 755" BSD_INSTALL_SCRIPT_DIR="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -d -m 755" BSD_INSTALL_DATA_DIR="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -d -m 755" BSD_INSTALL_MAN_DIR="/home/g/src/ports/pobj/fzf-0.21.1/bin/install -d -m 755" go install -v -p 1 github.com/junegunn/fzf github.com/junegunn/fzf/vendor/golang.org/x/sys/unix github.com/junegunn/fzf/vendor/github.com/mattn/go-isatty github.com/junegunn/fzf/vendor/github.com/mattn/go-runewidth github.com/junegunn/fzf/src/util github.com/junegunn/fzf/src/algo github.com/junegunn/fzf/vendor/golang.org/x/crypto/ssh/terminal github.com/junegunn/fzf/src/tui github.com/junegunn/fzf/vendor/github.com/mattn/go-shellwords github.com/junegunn/fzf/vendor/golang.org/x/sync/errgroup github.com/junegunn/fzf/vendor/github.com/saracen/walker github.com/junegunn/fzf/src github.com/junegunn/fzf/src/protector github.com/junegunn/fzf -f -- reach out /usr/bin/touch faith
github mirror
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
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 opened an issue:
https://github.com/junegunn/fzf/issues/1993
While trivial, it's annoying, and of course it might not make it into
upstream for whatever reason. For the time being I am proposing the
following local patch for constants.go:
--- constants.go.orig Sun Apr 19 20:40:59 2020
+++ constants.goSun Apr 19 20:41:36 2020
@@ -59,7 +59,7 @@
func init() {
if !util.IsWindows() {
- defaultCommand = `set -o pipefail; command find -L . -mindepth
1 \( -path '*/\.*' -o -fstype 'sysfs' -o -fstype 'devfs' -o -fstype 'devtmpfs'
-o -fstype'proc' \) -prune -o -type f -print -o -type l -print 2> /dev/null |
cut -b3-`
+ defaultCommand = `sh -c "command find -L . -mindepth 1 -path
'*/\.*' -prune -o -type f -print -o -type l -print 2> /dev/null | cut -b3-"`
} else if os.Getenv("TERM") == "cygwin" {
defaultCommand = `sh -c "command find -L . -mindepth 1 -path
'*/\.*' -prune -o -type f -print -o -type l -print 2> /dev/null | cut -b3-"`
}
2. i am a daily user of fzf, also from vim and nvim, integrated with
numerous plugins, but i dont appreciate the package (any package)
installing plugins into my vim runpath whether i asked for it or not.
(also it does not work by default with nvim). The documented and
recommended approach is to add the folder holding the `.vim` file as
another plugin (if used with `vim-plug` from the same author as fzf):
" e.g. on macOS:
Plug '/usr/local/opt/fzf' " <- `fzf.vim` from `brew install fzf`
Plug 'junegunn/fzf.vim' " <- the vim fzf plugin itself
So I think the more generic approach would be to install the `.vim`
file under `/usr/local/share/fzf/...` and use the vim/nvim settings to
discover and load it:
" openbsd:
Plug '/usr/local/share/fzf' " <- where the package should install
Plug 'junegunn/fzf.vim'
diff --git a/sysutils/fzf/Makefile b/sysutils/fzf/Makefile
index 1a807ae1c..94a704a1e 100644
--- a/sysutils/fzf/Makefile
+++ b/sysutils/fzf/Makefile
@@ -4,6 +4,8 @@ COMMENT = command-line fuzzy finder
DISTNAME = fzf-0.21.1
+REVISION = 0
+
CATEGORIES = sysutils
HOMEPAGE = https://github.com/junegunn/fzf
@@ -33,7 +35,7 @@ ALL_TARGET = github.com/junegunn/fzf
ZSH_SITE = ${PREFIX}/share/zsh/site-functions
FISH_SITE =${PREFIX}/share/fish/functions
BASH_SITE =${PREFIX}/share/fzf/bash
-VIMFILES = ${PREFIX}/share/vim/vimfiles
+VIMFILES = ${PREFIX}/share/fzf
VIM_PLUGIN = ${VIMFILES}/plugin
VIM_DOC = ${VIMFILES}/doc
SUBST_VARS += BASH_SITE FISH_SITE VIMFILES
--- PLIST.orig Sun Apr 19 18:16:45 2020
+++ PLIST Sun Apr 19 21:00:23 2020
@@ -11,12 +11,10 @@
share/fzf/bash/
share/fzf/bash/completion.bash
share/fzf/bash/key-bindings.bash
-share/vim/
-share/vim/vimfiles/
-share/vim/vimfiles/doc/
-share/vim/vimfiles/doc/fzf.txt
-share/vim/vimfiles/plugin/
-share/vim/vimfiles/plugin/fzf.vim
+share/fzf/doc/
+share/fzf/doc/fzf.txt
+share/fzf/plugin/
+share/fzf/plugin/fzf.vim
share/zsh/
share/zsh/site-functions/
share/zsh/site-functions/_fzf_completion
-f
--
a man serves best, when he serves himself.
Re: postgresql: libc collation issue, linking with ICU
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 "fr-FR-x-icu");
CREATE TABLE
macos=# INSERT INTO t (values ('bernard'),('bérénice'),('béatrice'),('boris'));
INSERT 0 4
macos=# SELECT * FROM t ORDER BY n;
n
--
béatrice
bérénice
bernard
boris
(4 rows)
macos=# show lc_collate;
lc_collate
C
(1 row)
macos=# \d t
Table "public.t"
Column | Type | Collation | Nullable | Default
+--+-+--+-
n | text | fr-FR-x-icu | |
however `CREATE DATABASE` and `initdb` does not support this. it's WIP:
https://www.postgresql-archive.org/ICU-for-global-collation-td6099973.html
it is far from ideal but at least having the option to override the
collation on both schema and/or individual query level means a working
sorting.
this is a good article when ICU was introduced:
https://www.2ndquadrant.com/en/blog/icu-support-postgresql-10/
(...i wonder what's the actual situation with mariadb...)
-f
--
tower: "say position." pilot: "position."
Re: postgresql: libc collation issue, linking with ICU
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 > > databases. Real world tests would probably help. > > I doubt it can have side effects on existing databases as they all have > a locale (and potential collations) configured during initdb, and adding > the possibility to use more locales/collations shouldnt affect existing > ones. Of course, to be tested in the real world :) initdb just sets "default" collation/ctype for `template1`. when collation/ctype needs to be different, `CREATE DATABASE` must use the template `template0`. Collation cannot be changed on a database after it has been created as it affects the index creation as well. -f -- why is the alphabet in that order? is it because of that song?
Re: postgresql: libc collation issue, linking with ICU
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 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 in the future, not even in the long term. Even > > >> sounds like all the more reason to build postgresql with ICU. > > > Nothing in Ingo's mail contradicts that. > > Right. it seems that we all agree.. as long as there is a strong case not to put locale aware collation into libc, using ICU with postgresql becomes more or less mandatory as there's not much use of a database server that cannot sort it's content... -f -- all computers wait at the same speed.
Re: postgresql: libc collation issue, linking with ICU
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 in the future, not even in the long term. Even sounds like all the more reason to build postgresql with ICU. -f -- my desk is a final proof of the chaos theory
Re: [NEW] fonts/firacode
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 any other way. fira and fira code and 2 seperate projects and should be treated as such.. unfortunately the latest major fira code update has some issues and shows up "strange" in certain terminal emulators, i personally had to roll back to the previous major version... https://github.com/tonsky/FiraCode/issues/833 -- i'm not overweight, i'm undertall! -- garfield
postgresql: libc collation issue, linking with ICU
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 ('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)
linux=# select n from (values ('bernard'),('bérénice'),('béatrice'),('boris'))
AS l(n) order by n collate "fr_FR"
n
béatrice
bérénice
bernard
boris
(4 rows)
postgres supports ICU and this guarantees the same results on every
platform. both macos and linux link against it, i think it would be a
good addition to the openbsd port as well...
macos=# select n from (values ('bernard'),('bérénice'),('béatrice'),('boris'))
AS l(n) order by n collate "fr-FR-x-icu";
n
--
béatrice
bérénice
bernard
boris
(4 rows)
macos=# SELECT * FROM pg_collation;
...
(861 rows)
linux=# select n from (values ('bernard'),('bérénice'),('béatrice'),('boris'))
AS l(n) order by n collate "fr-FR-x-icu";
n
béatrice
bérénice
bernard
boris
(4 rows)
linux=# SELECT * FROM pg_collation;
...
(1142 rows)
openbsd=# select n from (values
('bernard'),('bérénice'),('béatrice'),('boris')) AS l(n) order by n collate
"fr-FR-x-icu";
ERROR: collation "fr-FR-x-icu" for encoding "UTF8" does not exist
LINE 1: ...nice'),('béatrice'),('boris')) AS l(n) order by n collate "f...
^
openbsd=# SELECT * FROM pg_collation;
...
(134 rows)
not sure if related but sort(1) is similarly confused (also on macos):
$ echo $LC_CTYPE
en_US.UTF-8
$ cat n
bernard
boris
béatrice
bérénice
$ sort n
bernard
boris
béatrice
bérénice
-f
--
history doesn't repeat itself. historians do.
