* Any reason not to add elksnet + elkscmd?
@ 2015-03-05 14:57 Jody Bruchon
0 siblings, 0 replies; only message in thread
From: Jody Bruchon @ 2015-03-05 14:57 UTC (permalink / raw)
To: ELKS
Unless anyone on the list has objections, I'm planning to merge elksnet
and elkscmd. It seems silly to have all the other command-line tools in
elkscmd (including many ELKS-specific versions of programs) but then
have a tiny number of programs in a totally separate directory tree that
only serves to make the build system more needlessly complex than it
already is.
If the spirit of the original division was to keep them separated from
ports of "normal" programs, I could push them to a new directory
"elkscmd/elksnet" but it seems like "elkscmd/inet" would be just as good.
Any thoughts/preferences?
-Jody
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-03-05 14:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-05 14:57 Any reason not to add elksnet + elkscmd? Jody Bruchon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox