Previous: Shell Conventions, Up: Conventions [Contents]
Repository conventions are important in order to ensure every package resemble themselves. Here are the things to keep in mind:
Prefer tarballs over git packages unless there is a sensible reason. Here are some:
Prefer sources without a dependency to ‘automake’. There are usually distribution tarballs that are ‘autoconf’’ed. Don’t submit tarballs with an automake dependency unless you are ‘sure’ there is no alternative.
Avoid these packages:
Usually can be disabled by --disable-dbus
.
Usually can be disabled by --disable-nls
.
All build files on the repository should be a POSIX
shell script, and must start with #!/bin/sh -e
.
The next section is about package templates that should be used in order to ensure stylistic consistency. Note that the option configurations shouldn’t be taken literally, they are meant as examples.
#!/bin/sh -e make make DESTDIR="$1" PREFIX=/usr install
#!/bin/sh -e ./configure \ --prefix=/usr \ --disable-option \ --enable-option make make DESTDIR="$1" install
See 2020
#!/bin/sh -e autoreconf -fi ./configure \ --prefix=/usr \ --disable-option \ --enable-option make make DESTDIR="$1" install
#!/bin/sh -e export DESTDIR=$1 meson \ --prefix=/usr \ -Doption=false \ -Doption2=true \ . output ninja -C output ninja -C output install
#!/bin/sh -e export DESTDIR=$1 cmake -B build \ -DCMAKE_INSTALL_PREFIX=/usr \ -DCMAKE_BUILD_TYPE=Release \ -DOPTION=ON cmake --build build cmake --install build
#!/bin/sh -e export GOPATH=$PWD/gopath trap "go clean -modcache" EXIT INT go mod vendor go build install -Dm755 program "$1/usr/bin/program"
#!/bin/sh -e python setup.py build python setup.py install --prefix=/usr --root="$1"
Previous: Shell Conventions, Up: Conventions [Contents]