gisgeek, 5 months ago to linux

I'm old enough to have begun using #unix before #linux, and in the first years, I used *nix (well, SunOS, Solaris, and Digital OSF/1, to say more precisely) for so long. I'm what nowadays is considered a Veteran Unix Admin or #vua. I'm still curious enough to stay updated about current tech, but I wonder how many people out there in the #fediverse are still passionate about tech novelties but even cultivate legacy knowledge such as #C, #Perl, #Tcl, #autoconf and #automake, #m4 and above all why?

ArneBab, 8 months ago to random German

#gnu #autoconf / #automake tipp:

tar-ustar: use ustar format of tar (POSIX 1003.1-1988) to lift the

99 character limit on filenames (it is now 155 for the directory and

256-dir for the file). Needs Automake 1.9 or newer

see https://www.gnu.org/software/automake/manual/1.10/html_node/Options.html#index-Option_002c-tar_002dv7

and https://www.gnu.org/software/tar/manual/html_node/Formats.html#Formats

AM_INIT_AUTOMAKE([1.9 tar-ustar])

(this is planned to become a default in make dist—the limit is there to support some really old tar implementations—but currently the default is still tar-v7 with max 99 chars)

mattst88, 11 months ago to random

You know what's a "code smell" I've noticed?

A dirty git status after a build.

Even worse if the build modifies (or deletes!) files tracked by git.

Yes, I saw this today. And man, oh man, is the whole project smelly.