Request Midnight Commander File Manager

[Jason W]

egrep, fgrep, and grep added to localbin/ in mc.scm.

[SamK]

egrep, fgrep, and grep added to localbin/ in mc.scm.

When browsing an ISO an unmissable error message is obtained (see screenshot).  Upon cancelling the message the ISO directories and files are then presented.  Other than modifying the offending script is there a way to prevent the display of the message?
   

[Rich]

Hi SamK
Other than modifying the script, install  grep.tcz.

[SamK]

Hi SamK
Other than modifying the script, install  grep.tcz.

Hi Rich
Yes that does work.  Have a browse back to post #43 in the thread, it was the aproach I used it to help diagnose the problem.  As a fully self-contained app has been decided upon, the question is whether the misleading error message can be circumvented with grep built into the SCM as it is now.
   

Edit: typos

[Rich]

Hi SamK
The message is not misleading, the error just wasn't fatal so you could still view the ISO. There is still at least
one hard coded path to  /usr/local/bin/  in the iso9660 script. Execute:

Code: [Select]

grep "usr/local/bin" /apps/mc/libexec/mc/extfs.d/*If the app were self contained, you probably shouldn't get any results. So, besides fixing the script or installing
grep, I guess the only other possibility is creating a link to busyboxes grep in  /usr/local/bin/.

[SamK]

Hi Rich

The message is not misleading...

On the basis that it gives the impression that the requested action has/will fail, when it hasn't/won't, misleading is a fair description, however undesirable may be apt.

...I guess the only other possibility is creating a link to busyboxes grep in  /usr/local/bin/.

This looks as though it will work.  Not sure how it will be viewed in terms of an SCM creating the link during installation.
   

[Rich]

Hi SamK
Several other scripts in that directory call grep, but this is the only one that prepends a path onto it. The only
grep options I noticed being used in those scripts was -v, -i, -q, -s, and -c, which busybox grep supports.
Creating the link via the SCM is definitely not the right thing to do.

[Jason W]

It appears the issue would go away if grep and those other utiliites were available in /apps/mc/localbin when mc was being built, so the scripts would be right.  And preferably all build from scratch.

I will do that this week.

[Jason W]

For now I fixed the iso9660 script by replacing /usr/local/bin/grep with grep, so the grep in the extension that is in the set path will be used.

[gerald_clark]

Still doesn't open isos.

[SamK]

For now I fixed the iso9660 script by replacing /usr/local/bin/grep with grep, so the grep in the extension that is in the set path will be used.

Still doesn't open isos.

Applied the update and tested using Core-current.iso.  Works fine here. No error messages received, simply able to browse the contents.

[SamK]

Perhaps this post might be helpful in getting a fully oprtational SCM
http://forum.tinycorelinux.net/index.php/topic,13543.msg75221.html#msg75221

Using the Debian based machine:
Pressing <Enter> produces error free browsing of tgz, tar.gz, rar, iso, 7z, zip

Using TCv4.5.4
Pressing <Enter> produces error free browsing of rar, iso, 7z
Fails on  tgz, tar.gz, tar.bz2, zip

Error message tgz, tar.gz,

Code: [Select]

Cannot oper tar archive
NAME.tgz/ugz://
Error message tar.bz2,

Code: [Select]

Cannot oper tar archive
NAME.tar.bz2/ubz2://
Error message zip

Code: [Select]

Inconsistent extfs archive
sh: /apps/mc/libexec/mc/extfs.d/uzip: not found   

[gerald_clark]

The problem with the isos was:
Don't forget to delete the old ~/.config/mc.

[Jason W]

The unzip issue shows that mc simply needs to be rebuilt, with it's proper dependencies in place.

It is a shame that the cause of the difficulty of this MC package perhaps appears to readers of this thread to be it's scm format, when 90% of it is rather due to the fact that I was unfamiliar with MC, it's dependencies, and it's usage.

I will rebuild it with it's deps included when the opportunity arises.


 

[SamK]

It is a shame that the cause of the difficulty of this MC package perhaps appears to readers of this thread to be it's scm format, when 90% of it is rather due to the fact that I was unfamiliar with MC, it's dependencies, and it's usage.

Your willingness to produce an SCM of an app you are unfamiliar with is helpful and deserving of praise and encouragement.  This new to us all, there are bound to be minor hiccups along the way.

I would like to register my support and thanks for the effort you are making. The community is a better place as a result of it.