I was going to warn you that you're about to kick yourself, but I see
that Guillermo has already replied, so you're probably already kicking
yourself. (-:
fREW Schmidt:
First off, there's no README or anything, so I sorta have to guess.
[...] Again there's no README for redo.
As Guillermo said, the instructions for building from source are right
there on the WWW pages whence one downloads the source package.
*
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/source-package.html
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/redo.html
Both can be built either in the Debian way into installable packages,
with the Debian dpkg-buildpackage tool (with directories prepared with
package/debian/prepare); or as a self-contained package, slashpackage
style, with the conventional slashpackage commands.
FreeBSD/PC-BSD doesn't have Debian toolsets, but there's a bsd/rules
mechanism (prepared with package/bsd/prepare) available for building BSD
package files with a "Debian-like" system. Or one can build as a
self-contained package on BSD, too.
As Guillermo said, what you were fiddling with were actually internals
of the build system, that it sets up for you. All that you have to
remember, whether you choose self-contained package or Debian-esque
build, is one command line. It's *the same* command across nosh and
redo, moreover. (It is indeed the same command in daemontools,
UCSPI-SSL, ftpcopy, and others. I've also employed it in my own source
packages that I use for djbdns and publicfile.)
* http://www.superscript.com/ucspi-ssl/install.html
* https://ohse.de/uwe/ftpcopy/install.html
* http://www.fehcom.de/ipnet/ucspi-ssl.html
As the (nosh and redo) source package download and build instructions
pages say, slashpackage is a whole subject in its own right. One day I
might put up a FGA about it. But if one looks to other systems and
spots hierarchical package naming, self-contained build-trees, "current
version" symbolic links, atomic upgrades, and "index"/"alternatives"
directories one can see those all in slashpackage.
* https://news.ycombinator.com/item?id=10505897
It is not mine, but the invention of Some Bloke On Another Continent:
* http://cr.yp.to/slashpackage.html
He didn't really document the build process too well. It's the build
process that mainly concerns us, here. Some Other Bloke On A Different
Continent To The First Bloke wrote about that part in 2002, though:
*
https://web.archive.org/web/20021011214224/http://www.skarnet.org/software/compile.html
A Third Bloke On A Third Continent (at the time) also wrote about it in
2002:
* http://thedjbway.b0llix.net/builddjb.html#slashpackage
A Fourth Bloke even got in on the act:
* http://code.dogmap.org/slashpackage/
