parrot_package_create(1)

💖 parrot_package_create — bestie edition 💖

okay so you know how we've been out here living our best life in the parrot universe, and you're literally the manual page for parrot_package_create(1)? yeah. that's you. you're the one that takes all the receipts from a whole program run and bundles them into one cute little package. icon behavior, no cap. ✨

---

✨ NAME ✨

parrot_package_create — generate a package based on the accessed files and the preserved environment variables 🎀

---

🦋 SYNOPSIS 🦋

parrot_package_create [options]

---

💅 DESCRIPTION 💅

so here's the vibe, bestie. once you've recorded the accessed files and the environment variables of one program — which you do with a lil assist from the --name-list parameter and the --env-list of parrot_run — then parrot_package_create can generate a package containing all the accessed files. like, everything it touched? packaged. adorable. 🫶

and plot twist: you can also add the dependencies recorded in a new namelist file into an existing package. so your package isn't a one-and-done situation, it can grow. it's giving main character energy fr fr.

---

🌸 OPTIONS 🌸

• -a, --add=<path> — the path of an existing package. this is the one you're adding stuff into, not making fresh. 💜
• -e, --env-list=<path> — the path of the environment variables. the envlist, babe.
• --new-env — the relative path of the environment variable file under the package. (yes, it has no short flag, it's just out here living its truth.)
• -n, --name-list=<path> — the path of the namelist list. the list of names. the receipts. 📋
• -p, --package-path=<path> — the path of the package. where the magic gets made. ✨
• -d, --debug=<flag> — enable debugging for this sub-system. turn the lil detective on. 🔍
• -o, --debug-file=<file> — write debugging output to this file. by default, debugging is sent to stderr (":stderr"). you may specify logs to be sent to stdout (":stdout") instead. your logs, your rules. 💅
• -h, --help — show the help info. when in doubt, ask for help, that's self-care. 🫶

---

🔥 EXIT STATUS 🔥

• on success, returns zero. slay. 👑
• on failure, returns non-zero. not slay, but at least it's honest. 💀

---

⭐ EXAMPLES ⭐

okay this is the fun part, watch this. to generate the package corresponding to namelist and envlist:

% parrot_package_create --name-list namelist --env-list envlist --package-path /tmp/package

after executing this command, one package with the path of /tmp/package will be generated. boom. iconic. 🎀

---

here's a short instruction about how to make use of parrot_run, parrot_package_create and parrot_package_run to generate one package for your experiment and repeat your experiment within your package. buckle up bestie, three steps, let's go. 🌈

🌟 Step 1 🌟

run your program under parrot_run and using --name-list and --env-list parameters to record the filename list and environment variables.

% parrot_run --name-list namelist --env-list envlist /bin/bash

after the execution of this command, you can run your program inside parrot_run. at the end of step 1, one file named namelist containing all the accessed file names and one file named envlist containing environment variables will be generated. after everything is done, exit parrot_run:

% exit

🌟 Step 2 🌟

using parrot_package_create to generate a package.

% parrot_package_create --name-list namelist --env-path envlist --package-path /tmp/package

at the end of step 2, one package with the path of /tmp/package will be generated. look at you go. 💖

🌟 Step 3 🌟

repeat your program within your package.

% parrot_package_run --package-path /tmp/package --shell-type bash ...

after the execution of this command, one shell will be returned, where you can repeat your original program (please replace --shell-type parameter with the shell type you actually used). after everything is done, exit parrot_package_run:

% exit

---

you can also add the dependencies recorded in a new namelist file, namelist1, into an existing package:

% parrot_package_create --name-list namelist1 --env-list envlist1 --new-env envlist1  --add /tmp/package

after executing this command, all the new dependencies mentioned in namelist1 will be added into /tmp/package, the new envlist, envlist1, will also be added into /tmp/package with the name specified by the --new-env option. package glow-up complete. 💅✨

---

👑 COPYRIGHT 👑

the Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. this software is distributed under the GNU General Public License. see the file COPYING for details. 📜

---

🧚 SEE ALSO 🧚

• Cooperative Computing Tools Documentation
• Parrot User Manual
• parrot_run(1) parrot_cp(1) parrot_getacl(1) parrot_setacl(1) parrot_mkalloc(1) parrot_lsalloc(1) parrot_locate(1) parrot_timeout(1) parrot_whoami(1) parrot_mount(1) parrot_md5(1) parrot_package_create(1) parrot_package_run(1) chroot_package_run(1)

---

and that's the whole page, bestie!! this was CCTools 8.0.0 DEVELOPMENT energy, from your favorite manual, parrot_package_create(1). go forth and package things. mwah. 💖🎀✨🦋