Created attachment 213196 [details] .shar lsxo - A ls(1) clone supporting libxo output Built on: FreeBSD 13.0-CURRENT r352742 GENERIC amd64 Testing: * portlint -A * port test * poudriere testport -j 130Camd64 -p default -i -o sysutils/lsxo * poudriere testport -j 121Ramd64 -p default -i -o sysutils/lsxo (the utility has not dependencies)
Should we instead just add libxo support directly to "ls"? The whole point of using libxo is to have a single code path that supplies all output, so making a cloned command is the wrong direction. Is there something missing from libxo that makes this difficult for "ls"? Thanks, Phil
The ls utility was converted to use libxo base r284198, currently the support has been deleted base r328100 (discussion review D13959), however the svn repository still stores the last revision with libxo base r326025 in the history, so some user may take advantage of this feature by using this port.
lsxo is just a svn revision of `ls(1)`, it is linked in the `ls` row https://wiki.freebsd.org/LibXo.
I could delete the project repository in the future https://gitlab.com/alfix/lsxo