Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24067 - [mc] Add optional dependencies to mc package

Attached to Project: Community Packages
Opened by Kirill Churin (reflexing) - Tuesday, 03 May 2011, 13:50 GMT
Last edited by Jakob Gruber (schuay) - Sunday, 05 June 2011, 08:02 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Jakob Gruber (schuay)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Can you please add optional dependencies to the mc package, e.g. like in Debian (http://packages.debian.org/sid/mc) to see what tools needed for various mc's VFS functionality.

For example, it's obscure what should I install for iso9660 support.

Thanks.
This task depends upon

Closed by  Jakob Gruber (schuay)
Sunday, 05 June 2011, 08:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  optdeps have been added to trunk and will be released with the next mc version.
Comment by Greg (dolby) - Tuesday, 03 May 2011, 15:48 GMT
Just bear in mind the optdepends if you absolutely need to have an analogy are equivalent to recommended packages in Debian, not the suggested ones.
Comment by Kirill Churin (reflexing) - Tuesday, 03 May 2011, 15:59 GMT
My point is: it's just useful to see them during installing or # pacman -Qi'ing, whether it is suggested or recommended in Debian, i don't care about Debian, I care about Arch :)
Comment by Greg (dolby) - Tuesday, 03 May 2011, 16:08 GMT
My previous comment was not intirely correct.  FS#13282  holds some of the details of how optdepends are used. But i guess its up to the maintainer.
EDIT: But, if you're gonna provide an informative message (cause thats what optdepends are until today) for iso9660 support, are you gonna provide for all * support? MC might need quite a lot of those. Just look in the /usr/lib/mc/extfs.d/ directory ...
Comment by Kirill Churin (reflexing) - Tuesday, 03 May 2011, 16:18 GMT
Maybe it'll be nice to point user to this directory then?..
Comment by Jakob Gruber (schuay) - Tuesday, 31 May 2011, 14:07 GMT
When I try to open a *.ace file file in mc, I get a message "/usr/lib/mc/extfs.d/uace: line 24: unace: command not found".

There are tools around which allow finding the package that contains a given file, and it should be easy enough to figure out the deps for your used extensions.

So at the moment I'm hesitant about both 1) adding optdeps or 2) adding a post install message.
Comment by Kirill Churin (reflexing) - Wednesday, 01 June 2011, 10:43 GMT
Maybe it's worth trying to ask wise arch community @ arch-general ML? :)

I personally vote for optdepends.
Comment by Jakob Gruber (schuay) - Saturday, 04 June 2011, 17:29 GMT
On second thought, optdeps sounds fine. How does this list look?

mtools: a+
cdparanoia: audio
gawk: hp48+
cdrkit: iso9660
perl: several extfs scripts
python-boto: s3+
python2-pytz: s3+
p7zip: u7z
unace: uace
unarj: uarj
cabextract: ucab
unrar: urar
zip: uzip
Comment by Kirill Churin (reflexing) - Saturday, 04 June 2011, 20:50 GMT
I think it's good, but why do you prepend some dep names with 'un'? I think it should be like this:

rar: urar
cab: cabextract
archive/whatever type: program to handle it
Comment by Jakob Gruber (schuay) - Saturday, 04 June 2011, 20:59 GMT
Because that's what these packages are actually called in arch. Packages are on the left, extfs plugin names on the right.
Comment by Kirill Churin (reflexing) - Saturday, 04 June 2011, 21:01 GMT
Ughhhh, sorry ) then it's perfect!

Loading...