FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux Pacman Development

 
 
LinkBack Thread Tools
 
Old 05-27-2008, 07:39 PM
"Dan McGee"
 
Default Use "legacy mode" for `file` on Mac OSX

On Tue, May 27, 2008 at 2:23 PM, Sebastian Nowicki <sebnow@gmail.com> wrote:
> For some reason `file` on Mac OSX has different arguments than BSD and
> Linux; -i no longer prints out the mime strings. With the environment
> variable COMMAND_MODE set to "legacy", `file` behaves more like it does
> on Linux and BSD, i.e., `file -i` prints the mime type.
>
> Signed-off-by: Sebastian Nowicki <sebnow@gmail.com>
> ---
> scripts/makepkg.sh.in | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
> index 91b05f1..aa0b99e 100644
> --- a/scripts/makepkg.sh.in
> +++ b/scripts/makepkg.sh.in
> @@ -32,6 +32,8 @@
> # gettext initialization
> export TEXTDOMAIN='pacman'
> export TEXTDOMAINDIR='@localedir@'
> +# necessary to achieve consistent behavior for `file` on Mac OSX
> +export COMMAND_MODE=legacy
Use ' (quotes) like every other variable here, but otherwise looks
fine. I think this is the best solution to the problem.
And concise is fine:
# file -i is broken on Mac OSX unless legacy mode is set
or at least I consider it broken.
>
> myver='@PACKAGE_VERSION@'
> confdir='@sysconfdir@'
> --
Acked-by: Dan McGee <dan@archlinux.org>

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 05-27-2008, 07:48 PM
"Aaron Griffin"
 
Default Use "legacy mode" for `file` on Mac OSX

On Tue, May 27, 2008 at 2:39 PM, Dan McGee <dpmcgee@gmail.com> wrote:
> On Tue, May 27, 2008 at 2:23 PM, Sebastian Nowicki <sebnow@gmail.com> wrote:
>> For some reason `file` on Mac OSX has different arguments than BSD and
>> Linux; -i no longer prints out the mime strings. With the environment
>> variable COMMAND_MODE set to "legacy", `file` behaves more like it does
>> on Linux and BSD, i.e., `file -i` prints the mime type.
>>
>> Signed-off-by: Sebastian Nowicki <sebnow@gmail.com>
>> ---
>> scripts/makepkg.sh.in | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
>> index 91b05f1..aa0b99e 100644
>> --- a/scripts/makepkg.sh.in
>> +++ b/scripts/makepkg.sh.in
>> @@ -32,6 +32,8 @@
>> # gettext initialization
>> export TEXTDOMAIN='pacman'
>> export TEXTDOMAINDIR='@localedir@'
>> +# necessary to achieve consistent behavior for `file` on Mac OSX
>> +export COMMAND_MODE=legacy
> Use ' (quotes) like every other variable here, but otherwise looks
> fine. I think this is the best solution to the problem.
> And concise is fine:
> # file -i is broken on Mac OSX unless legacy mode is set
> or at least I consider it broken.
>>
>> myver='@PACKAGE_VERSION@'
>> confdir='@sysconfdir@'
>> --
> Acked-by: Dan McGee <dan@archlinux.org>

Ack to Dan's comments.
Acked-by: Aaron Griffin <aaronmgriffin@gmail.com>

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 

Thread Tools




All times are GMT. The time now is 04:00 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org