On Sat, Jun 23 2018, Brian Callahan <[email protected]> wrote: > Hi ports -- > > Attached is a new port, sysutils/seq. seq is a utility to print sequences of > numbers. > > --- > pkg/DESCR: > The seq utility prints a sequence of numbers, one per line, from an > optional initial value (default 1) to a final value, in increments of an > optional increment value (default 1). When the final value is larger > than the initial value, the default increment value is -1. > > It is a port of the seq utility from FreeBSD. > --- > > The other 3 BSDs have this utility in their base systems. No, I'm not > advocating for that. And yes, one could install GNU coreutils and get > gseq. But I see this utility used around enough that it's worth it for > me to maintain a port of it.
What makes it worth a new, separate port? People could just install coreutils and use gseq. Is that version at least reasonably compatible with GNU seq? If not, providing this as a package named "seq" would be misleading, maybe "freebsd-seq" would be more appropriate. > Chose FreeBSD because it appears most > maintained. > > Numbered as it is because I took it from the tip of FreeBSD's tree. > > OK? Do you know what would be the impact on the ports tree? It would be a PITA if some ports started using this port at build time and then fail because of dpb(1) junking. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
