SHAPE_TAR(1)

🎀 NAME 🎀

okay so bestie, meet shape_tar — the shapeTools RMS bundle-up subsystem, except it bundles everything into a tar or a shar archive. iconic behaviour honestly ✨

🌸 SYNOPSIS 🌸

shape tar[VERSIONS=<version_selection_rule>] [ARCHIVE=<filename>]

shape shar[VERSIONS=<version_selection_rule>] [ARCHIVE=<filename>]

like. two whole moods. pick your fighter 💅

💖 DESCRIPTION 💖

so shape tar and shape shar literally build you a tar or a shar archive holding all the source components of the current node in the system tree. everything listed in the COMPONENTS macro in the Makefile gets written in, plus the release identification file (VERSIONFILE) too. no cap 🫶

heads up bestie: components of subsystems are NOT included in the archive file. like, they're simply not invited to the party 🙈

✨ VERSIONS ✨

the VERSIONS macro can be set to specify a version selection rule that stays active while the archive file is being created. the default is most_recent, which picks the most recent version of each component — main character behaviour, obviously 👑

for other possible settings, go peek at shape_stdrul(7) or the $(SHAPELIBPATH)/stdrules. and yes, you can absolutely use self defined version selection rules as VERSIONS too. do your own thing, we love that for you 💜

🦋 ARCHIVE 🦋

ARCHIVE is the base name of the file where the output shall be written. the default is $(SUBSYSTEMNAME). your output file then gets the filename extension .tar (resp. .shar). 🎀

and when ARCHIVE=- is given? data gets written to standard output. slay. streaming. periodt 🌈

🍓 SEE ALSO 🍓

• shape_RMS(1)
• shape_stdrul(7)

go read those too, iykyk 📚✨

🌟 FILES 🌟

• $(SUBSYSTEMNAME).tar
• $(SUBSYSTEMNAME).shar

look at them. your babies. 💅

okay that's the whole page bestie, tysm for reading 🥹💖 this was the shapeTools RMS bundle up subsystem situation, version 12.10.126, dated 12.10.126 — catch you in the next manpage, mwah 🎀🦋🌸