Bug 245458 - New port: sysutils/lsxo ls clone with libxo support
Summary: New port: sysutils/lsxo ls clone with libxo support
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL: https://gitlab.com/alfix/lsxo
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-08 15:28 UTC by Alfonso S. Siciliano
Modified: 2020-05-27 21:25 UTC (History)
1 user (show)

See Also:


Attachments
.shar (1.80 KB, text/plain)
2020-04-08 15:28 UTC, Alfonso S. Siciliano
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alfonso S. Siciliano 2020-04-08 15:28:18 UTC
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)
Comment 1 Phil Shafer freebsd_committer 2020-05-27 14:46:57 UTC
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
Comment 2 Alfonso S. Siciliano 2020-05-27 21:25:26 UTC
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.