Re: [gentoo-portage-dev] Perl, sort, and locale
[EMAIL PROTECTED] schrieb: I doubt this is the right place to bring this up, but maybe some one can tell me where to go :-) Yeah, this is definitely the wrong place, not really sure where the appropriate place for this is though. Probably a perl or coreutils related list/forum might help you. I have discovered an inconsistency in how perl and sort handle locale. Here are two commands you can run in a shell ... (echo '/'; echo '?') | sort (echo '/'; echo '?') | perl -e '@x = <>; print $_ foreach sort @x' With LANG=en_US.UTF-8, sort says ? comes before /, perl says the opposite. Setting LC_COLLATE=C switches the sort behavior. I have no idea what else changes or where else perl and sort disagree, or what other programs do. Seems like something is wrong, but I don't know what. This happens on other versions of Linux. It is not a gentoo specific problem. -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] Perl, sort, and locale
[EMAIL PROTECTED] wrote: > Seems like something is wrong, but I don't know what. This happens on > other versions of Linux. It is not a gentoo specific problem. > IIRC the locale issue is known, but it would be best to contact upstream (GNU?) in this case. Many of the problems in portage are solved by wrapping the call in LC_ALL="C" or something similar, AFAIK. -- gentoo-portage-dev@gentoo.org mailing list
[gentoo-portage-dev] Perl, sort, and locale
I doubt this is the right place to bring this up, but maybe some one can tell me where to go :-) I have discovered an inconsistency in how perl and sort handle locale. Here are two commands you can run in a shell ... (echo '/'; echo '?') | sort (echo '/'; echo '?') | perl -e '@x = <>; print $_ foreach sort @x' With LANG=en_US.UTF-8, sort says ? comes before /, perl says the opposite. Setting LC_COLLATE=C switches the sort behavior. I have no idea what else changes or where else perl and sort disagree, or what other programs do. Seems like something is wrong, but I don't know what. This happens on other versions of Linux. It is not a gentoo specific problem. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] feature freeze for 2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Stelling wrote: > Zac Medico wrote: >> the addition of new features. From this time forward, please do not >> commit anything to the 2.1 branch (current trunk) unless it is a fix >> for functionality that already exists. Thank you in advance for >> your cooperation. > > Why don't we make 2.1 a real branch and use trunk for 2.2? > If there's a need to have immediate activity in the 2.2 branch then we certainly should. If not, it's just extra work to merge stuff between the two. Zac -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEWOTQ/ejvha5XGaMRAlYoAJ0S1gQkUDBuHOfxZlYP1t5aWy/kAACbBeYO 3trOZs5yTGe2ftzTbRr0cZw= =Yof5 -END PGP SIGNATURE- -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] feature freeze for 2.1
Zac Medico wrote: the addition of new features. From this time forward, please do not commit anything to the 2.1 branch (current trunk) unless it is a fix for functionality that already exists. Thank you in advance for your cooperation. Why don't we make 2.1 a real branch and use trunk for 2.2? -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer -- gentoo-portage-dev@gentoo.org mailing list
