[SOLVED] /etc/nanorc empty after last current updates
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
nano.SlackBuild fails to generate nanorc.new because the source for this file has been renamed from nanorc.sample to sample.nanorc :
Code:
$ ls nano-2.6.0/doc/*nanorc*
nano-2.6.0/doc/nanorc.sample nano-2.6.0/doc/nanorc.sample.in
...
$ ls nano-2.7.4/doc/*nanorc*
nano-2.7.4/doc/nanorc.5 nano-2.7.4/doc/sample.nanorc
nano-2.7.4/doc/nanorc.5.html nano-2.7.4/doc/sample.nanorc.in
$ grep nanorc.new nano.SlackBuild
sed 's?^# include?include?g' doc/nanorc.sample > $PKG/etc/nanorc.new
$ ./nano.SlackBuild
....
make[2]: Leaving directory `/tmp/nano-2.7.4'
make[1]: Leaving directory `/tmp/nano-2.7.4'
mkdir: created directory ‘/tmp/package-nano/etc’
sed: can't read doc/nanorc.sample: No such file or directory
cp: cannot stat ‘BUGS’: No such file or directory
cp: cannot stat ‘UPGRADE’: No such file or directory
cp: cannot stat ‘doc/nanorc.sample’: No such file or directory
...
--
SeB
Last edited by phenixia2003; 01-12-2017 at 10:29 AM.
Subversion 1.7.22 (in 14.0 and probably 14.1 as well): ruby language binding fails to build
And now Nano.
Most SBo scripts actually do a "set -e".
Careful, the goal of SBo was to not differ from Slackware's SlackBuilds and then having users question Pat's scripts
Quote:
For that reason, the golden rule was established that all SlackBuild entries at slackbuilds.org would follow the style of the “mother” scripts. Basically, a SBo script should be transferable into the Slackware core distro without feeling out of place. I think it was this rule that made Pat give the nod of approval. Just think of the scenario where the SBo site would become popular using a style of SlackBuild scripts that did not look at all like Slackware’s own. There was a good chance that people would start demanding that Slackware must adopt the scripting style of SBo. This was a big no-no.
NOTE: I don't think that a minor change like set -e was what they were thinking of when they were intending to not differ from the "mother" scripts and I said the above jokingly. Overall, it probably wouldn't be a bad idea for Pat to incorporate set -e into future versions of his SlackBuild scripts, but as always, it's his distro, so we'll see what happens.
Subversion 1.7.22 (in 14.0 and probably 14.1 as well): ruby language binding fails to build
And now Nano.
Most SBo scripts actually do a "set -e".
If it is supposed to be a fatal error, I use || exit 1 after the command. But "set -e" does not work well when an error should be considered "soft" -- for example, I like to try to pack up any documentation file that's ever been seen in the sources, and don't want to have to edit that list when a file disappears. And if it's only gone for one release, editing the list could cause it to be dropped if it returns.
Basically, there are pros and cons to either approach, but I prefer to handle erroring out line by line.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.