Bug#913788: 9base: should mk diserve its own package?
Package: 9base
Version: 1:6-7+b1
Severity: wishlist
Dear 9base maintainers,
mk meant to be the "a Successor to Make" (Tenth Edition Research Unix
Manuals) and as mkfiles much more easier to maintain than the makefiles,
i actually replaced make in my projects. Shipping those ones, i realize
that mk is:
* hidden in the 9base package, giving it few chances to be noticed by
debian users.
* installed /usr/lib/plan9/bin/mk so you need to symlink it somewhere in
the $PATH to be used after the package installation.
i think mk deserve it's own package and i would be pleased to help to
make it happen but i don't know the best way to do it.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages 9base depends on:
ii libc6 2.27-8
9base recommends no packages.
Versions of packages 9base suggests:
pn wmii2 <none>
-- no debconf information
Reply to: