id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	branch_state	votes
2997	mc does not support autodetection for extfs - problem with different formats of .ipk files (now with patch)	cracket		"There is a problem with .ipk files support in mc, mainly because one extension .ipk can have two different formats. First format is tar.gz archive which is currently supported by mc. However second format is based on ar, and archives in this format are provided by some openembedded distributions. Unfortunatelly ar does not support tar archives and vice versa. 

To support both formats with same extension mc should have sort of ""autodetection"" or fallback if first extension returned with error code, because currently trying to browse or ""enter"" ipk archive triggers error:

{{{
tar: To nie wygląda jak archiwum tar
tar: Przeskoczenie do następnego nagłówka
tar: Zakończenie w stanie błędu z powodu uprzednich błędów
}}}
or without my polish locale:


{{{
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
}}}



Short workaround for supporting ar ipk files is to put in mc.ext section:

{{{
regex/\.ipk$
        Open=%cd %p#uar
        View=%view{ascii} ar t %f
}}}


and remove ipk from other sections

I attach ""ar"" ipk example file, the examples of ""tar"" ipk files are attached here: [http://www.midnight-commander.org/ticket/2925]
"	enhancement	new	major	Future Releases	mc-vfs	4.7.0		ipk ar tar vfs				no branch