On Wed, 26 Nov 2025 21:46:03 +0000, Stuart Henderson wrote:
> On 2025/11/26 21:16, Pascal Stumpf wrote:
> > CookCLI provides a suite of commands to create shopping lists,
> > reports and maintain recipes. We've built it to be simple and useful
> > for automating your cooking and shopping routine with existing UNIX
> > command line and scripting tools. It can also function as a webserver
> > for your recipes, making them browsable on any device with a web
> > browser.
> > 
> > This port is split into -main, which contains the "cook" binary, and
> > -server, which has the boilerplate to run a simple local "cook server"
> > from a system-wide recipe database (idea from ian@).
> > 
> > I previously imported textproc/cooklang-chef, but the original
> > cooklang-cli project has gained many of the features that made me prefer
> > "chef".
> > 
> > This reuses the uid/gid of sysutils/heartbeat, removed in 2012.
> 
> 
> I don't understand the advantage of using one package for the binary and
> one for 2 empty dirs, an rcscript, a readme, and a new user. Why not all
> in one?

I was thinking of users who might not want all of that, and would just
like to use the parsing / formatting features of the program.  Invoking
"cook recipe bigbeautifulenglishbreakfast.cook" doesn't need a separate
user.