CDE(1)

👑 CDE(1) — the manual page, but make it make sense 💅

okay bestie, section 1 of the manual, "User Commands", you already know ✨

🌸 NAME 🌸

cde — package everything required to execute a Linux command on another computer 🫶

Like. everything. all the bits. so it actually runs over there. iconic behaviour fr fr.

🦋 DESCRIPTION 🦋

CDE: Code, Data, and Environment packaging for Linux

Copyright 2010-2011 Philip Guo (pg@cs.stanford.edu) http://www.stanford.edu/~pgbovine/cde.html

the way that this tool just grabs your whole vibe and teleports it to another machine… no cap, that's the whole thing 💖

usage:

cde [command to run and package]

you hand it a command, it does its thing. periodt.

✨ Options ✨

• -c — prints the order of files copied into the package, and it writes that out into cde-copied-files.log 📝 so you can literally see the receipts of what got packed.
• -o <output dir> — sets a custom output directory instead of the default "cde-package/". so if you don't vibe with cde-package/, you get to pick your own spot 🎀
• -f — does NOT follow forks, which means child processes do not get packaged. so if your thing spawns lil baby processes, they are getting left behind 🙈 heads up.
• -i '<file path>' — ignore that exact file path. one specific file, one specific path, skipped 💅
• -p '<file path>' — ignore that file path prefix. so it's not just one file, it's the whole little family of paths starting with that prefix 🦋
• -v — verbose mode, for debugging 🔥 when you need it to spill every single detail.

🌈 SEE ALSO 🌈

cde-exec(1) — go read that one next bestie, it's the other half of the story 👑

and that's the whole page!! 💜 this was cde 0.1, dated February 2012, living in section CDE(1) of the manual. mwah, ily, go package something 🫶✨