|
From: | Boud Roukema |
Subject: | [task #15682] maneage-lint: check for host system shebang lines in executable scripts |
Date: | Mon, 8 Jun 2020 21:41:58 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 |
URL: <https://savannah.nongnu.org/task/?15682> Summary: maneage-lint: check for host system shebang lines in executable scripts Project: Reproducible paper template Submitted by: boud Submitted on: Tue 09 Jun 2020 01:41:57 AM UTC Should Start On: Tue 09 Jun 2020 12:00:00 AM UTC Should be Finished on: Tue 09 Jun 2020 12:00:00 AM UTC Category: None Priority: 5 - Normal Status: None Privacy: Public Percent Complete: 0% Assigned to: None Open/Closed: Open Discussion Lock: Any Effort: 0.00 _______________________________________________________ Details: I suspect that both a lot of science-level software and some system-level software uses scripts that have _#!/bin/bash_ or _#!/bin/sh_ or _#!/usr/bin/perl -w_ or _#!/usr/bin/env python_ in their shebang <https://en.wikipedia.org/wiki/shebang> lines. We could probably create a checklist _lint_ type script to help people find these and consider switching to the _maneage_ versions rather than the host versions. This would increase the probability of both portability and long-term reproducibility. The lint script should also add various other tests that we find are useful. For the moment, this could be an example to find some of these shebang scripts: for i in $(file .build/software/installed/bin/*|grep script |awk '{print $1}' |tr -d ':'); do printf "${i} ::: " ; head -n1 $i ; done _______________________________________________________ Reply to this item at: <https://savannah.nongnu.org/task/?15682> _______________________________________________ Message sent via Savannah https://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |