PORTBUMP(1)

portbump(1) 💅✨

okay so bestie, welcome to portbump — the General Commands Manual page that's about to make your whole ports tree look cute. no cap, this one's a little icon. 🎀

---

🌸 NAME 🌸

portbump — tweaks port revisions and library versions. that's the whole vibe. it bumps stuff. it slays. periodt. 🔥

---

🦋 SYNOPSIS 🦋

portbump [-lMmnrv] [-W wlib] [-w wlib] [portref ...]

portbump -o file [-lMmnrv] [-W addlib] [-w rmlib] [portref ...]

like, those two lines are literally the whole recipe. keep them safe. 🫶

---

💖 DESCRIPTION 💖

so portbump is the tool you reach for when you need to increase (aka "bump", iykyk) the REVISION and SHARED_LIBS values over in OpenBSD ports. it can also delete REVISION marks, and add, update, or remove WANTLIB items. it's giving multitasking main character energy, honestly. 👑

portref has the exact same syntax as the FULLPKGPATH port variable — go peek at bsd.port.mk(5) if you need the details, bestie. and yes, you can literally feed it a whole list of pkgpaths as parameters; any flavor info just gets ignored, no hard feelings. portbump also does not care at all about the actual subdirectory portion of portref, so you can freely pass ., ../foo, or honestly anything else like that. it's not judging. 💅

if a subpackage isn't specified in the port reference, then all subpackages of that port get processed. and if you give it no port references at all? it just processes the port in the current directory. lowkey convenient. ✨

the default mode of operation is increasing REVISION mark values (-r). and here's the cute part: you can combine operations on REVISION marks with operations on SHARED_LIBS by explicitly specifying the corresponding flags. see below, babes. 🎀

the following options are available:

---

⭐ OPTIONS ⭐

• -d — deletes all REVISION marks in the Makefile. mutually exclusive with -r, so pick a lane. 🙈
• -l — recreates all WANTLIB items based on the output of make port-lib-depends-check. and if you use it twice or more? then the make lib-depends-check gets used instead. plot twist. 😭 the -l mode is incompatible with -W and -w, so don't try to combine them, it's not that kind of party.
• -M — increments by one the major component of all SHARED_LIBS, resetting the minor one to zero if needed. mutually exclusive with -m. 🔥
• -m — increments by one the minor component of all SHARED_LIBS. mutually exclusive with -M. 💀
• -n — do not replace the Makefile; instead it saves the modified version in Makefile.bump. respectful. we love a non-destructive queen. 🌸
• -o file — sends the modified Makefile contents to the given file instead of creating Makefile.bump in the port's directory. heads up though: this can only be used if not more than one port is specified. multiple subpackages of a single port can still be specified, though. so like, one port, many subpackages, that's fine. 🫶
• -r — increments REVISION values for all subpackages, or only for the given ones. mutually exclusive with -d. this is the default btw, in case you forgot already. 💜
• -W wlib
• -w wlib — these two are a duo, so listen up: -W adds or updates WANTLIB items, and -w removes them — either in the whole port, or in particular subpackages if you gave any. both options can be specified multiple times, and they accumulate their corresponding lists. the WANTLIB entries get fully re-generated based on the previous contents. both of these modes are incompatible with -l. 🔥
• -v — enables printing of diagnostic messages to standard error output. very "tell me everything" of you. we support it. ✨

---

🧚 HISTORY 🧚

portbump first appeared in OpenBSD 5.6. a legend from the start, honestly. 👑

---

ok that's the whole page bestie, go forth and bump responsibly 💖

---

and that's a wrap! 🎀 this cutie came from the Debian crowd, dated June 26, 2018 — so like, vintage but still iconic. mwah. 💅✨