After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726182 - The unzip and tar commands are not in path with FreeBSD
The unzip and tar commands are not in path with FreeBSD
Status: RESOLVED OBSOLETE
Product: file-roller
Classification: Applications
Component: general
unspecified
Other FreeBSD
: Normal normal
: ---
Assigned To: file-roller-maint
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2014-03-12 15:55 UTC by Gustau Pérez i Querol
Modified: 2020-11-11 19:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Using unzip and tar from /usr/local/bin instead of the versions in /usr/bin (1.83 KB, patch)
2014-03-12 16:07 UTC, Gustau Pérez i Querol
rejected Details | Review

Description Gustau Pérez i Querol 2014-03-12 15:55:33 UTC
Those commands are not in the path of file-roller. One solution would be to use $PATH. Another one is in attachment that also fixes the problem.
Comment 1 Gustau Pérez i Querol 2014-03-12 16:07:38 UTC
Created attachment 271612 [details] [review]
Using unzip and tar from /usr/local/bin instead of the versions in /usr/bin
Comment 2 Allison Karlitskaya (desrt) 2014-06-28 15:10:40 UTC
Comment on attachment 271612 [details] [review]
Using unzip and tar from /usr/local/bin instead of the versions in /usr/bin

This is not an elegant approach.  Please change this to be based on $PATH, as you suggest.

Another alternative would be to detect the path to unzip at ./configure time and use that.

Please no hardcoding of OS-specific values like this...
Comment 3 Robert Roth 2015-01-02 13:25:09 UTC
Ryan's suggestion of detecting/configuring the path to unzip (and other tools) at .configure time is also reported in bug 133993, and I feel that fixing that properly would also fix this, as the FreeBSD port could be compiled with the proper .configure options and would work perfectly.
Based on the above maybe this as duplicate of bug 133993, and should be marked as such.
Comment 4 Paolo Bacchilega 2015-02-15 11:23:44 UTC
I would like to use g_find_program_in_path to fix this, but it is marked as deprecated, does anyone know the reason?
Comment 5 André Klapper 2020-11-11 19:12:25 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use file-roller and if you still see this bug / want this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/file-roller/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (volunteer workforce and time is limited).