pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Old octave issue

And it's faithful companion the invalid assumption...

If I recall, this is related to one of the issues I hit when building on CentOS a while back.

Do you know of a direct way of detecting whether charset_alias is needed, rather than assuming base on the OS?

Thanks for tracking this down.


On 08/08/16 07:52, Patrick Welche wrote:
On Tue, Oct 21, 2014 at 08:15:39AM -0400, Greg Troxel wrote:
I don't understand the charset.alias issue.   It seems that there's
something going on with iconv or similar where packages choose to
install a charset.alias depending on something else.
The something else turned out to be interesting. From:

	if test $(GLIBC21) = no; then \
	  case '$(host_os)' in \
	    darwin[56]*) \
	      need_charset_alias=true ;; \
	    darwin* | cygwin* | mingw* | pw32* | cegcc*) \
	      need_charset_alias=false ;; \
	    *) \
	      need_charset_alias=true ;; \
	  esac ; \
	else \
	  need_charset_alias=false ; \

We seem to have our old friend the hand coded list of operating system names.

There are two
approaches to deal with this.   One is to make conditional PLIST entries
to register the file on platforms that create it.  The other is to
understand and fix the root cause of the variance.   I think we should
figure out and fix the issue.  This is partly because I think it will be
easier in the long run, and partly becuase installation of files that
aren't about the package itself will lead to odd conflicts.
It appears that the current solution is to not install it by removing
it from the PLIST, as /usr/pkg/lib/charset.alias is listed in



All wars are civil wars, because all men are brothers ... Each one owes
infinitely more to the human race than to the particular country in
which he was born.
                -- Francois Fenelon

Home | Main Index | Thread Index | Old Index