This is the dérive ports tree.

since there isn't extensive information on how to create ports on the website, it will be summarized here.

0. to get started with porting, you should...

   • learn detour
   • see other ports and their dmake.sh

1. scripts
   derive "port scripts" (dmake.sh) are (kinda) simple. there are 4 targets that need to be tackled.

   • clean - removes a build directory for a package
   • make - fetches the source of and compiles a package
   • install - installs a package (it must be built!)
   • remove - removes a package (it must be built!)

2. running scripts
   there are two ways to run a dmake.sh

   1. doing it with detour [reccomended] this is the most simplest way, (the latter is too) you just run detour m(ic) <package>
      such script [m]akes, [i]nstalls and [c]leans a package. this also tracks the package's installed files, automatically resolves dependencies, and allows for easy package removal later.
   2. doing it the traditional way
      you navigate to your package, like cd /ports/core/curl and run

      sh dmake.sh make
      sh dmake.sh install
      sh dmake.sh clean # if you want
      

   this does not resolve dependencies or track packages, you will have to do it yourself.

3. understanding ports
   this section explains ports itself

   1. core
      the core/ directory has packages that NEED to be in the base system.
      they can range from compiler tools to something like git. nevertheless, most are needed in the base system.
   2. extra
      the extra/ directory has packages that are like "eh, its up to you".
      usually, there is choice in the set of packages, like eiwd and wpa_supplicant being provided even though they do the same thing. one wouldnt need most of these packages for a minimal system.
   3. firmware
      the firmware/ directory has packages that are sometimes needed for certain devices. firmware being mostly blobs for a variety of devices, currently only gpus and linux-firmware.

https://derivelinux.org/ports