What I mean is I was going to open a bug in sourceforge on the bug tracker for 
fink and the content of the explanation is prefilled with a note that says, 
"You can add a bug here but mostly we discuss these things on 
[email protected]".  If that's incorrect I'm more than happy to 
re-open a bug report in the sourceforge system but in that case I would ask 
that the note be taken out of the bug system so folks know where to report 
things.

Fink uses gnu's sed and as I understand it follows debian's packaging.  The 
same version of sed (4.2.1) works on my ubuntu install so, in general, it's not 
an issue with the gnu code.  That leaves the compilation of sed as specific to 
the 10.7 install.  Since I notice fink doesn't just install pre-made packages 
but does a compile for each, fink seemed the natural place to report a bug that 
seems related to the compilation options.

I did in fact start with the git team since I believe that a system's sed 
should be the preferred one for a widely used software system and if there are 
errors the application should address them, work around them, or choose a new 
method to achieve it's goals.  What I got from the git team was a lot of, "You 
seem to be asking for a nail but there's no way we would give you the kingdom." 
 It was quite frustrating but from the conversation I was able to resolve the 
issue and my development team can continue to make progress.

In the end my stuff works and that's good enough for my purposes.  I've tried 
to be a good open-source citizen and report problems to the teams that might 
have some stake in knowing about or resolving an unexpected bit of behavior.  
Please let me know if I should go back to the sourceforge bugtracker.

  Regards,
  -ljr

---
Lanny Ripple
[email protected]


On May 31, 2012, at 3:36 PM, Alexander Hansen wrote:

> On 5/31/12 12:14 PM, Lanny Ripple wrote:
>> Git uses the sed found on the PATH in git-am.  When using sed compiled by 
>> fink it gives incorrect results.
>> 
>> System sed (expected):
>> 
>>  lanny;~> echo "Rémi Leblond" | LANG=C LC_ALL=C /usr/bin/sed -ne 
>> 's/.*/GIT_AUTHOR_NAME='\''&'\''/p'
>>  GIT_AUTHOR_NAME='Rémi Leblond'
>> 
>> fink sed (unexpected.  .* breaks at é):
>> 
>>  lanny;~> echo "Rémi Leblond" | LANG=C LC_ALL=C /sw/bin/sed -ne 
>> 's/.*/GIT_AUTHOR_NAME='\''&'\''/p'
>>  GIT_AUTHOR_NAME='R'émi Leblond
>> 
>> This causes git rebase to fail.
>> 
>> OSX version 10.7.4
>> fink version
>>  Package manager version: 0.32.6
>>  Distribution version: selfupdate-rsync Thu May 31 14:12:29 2012, 10.7, 
>> x86_64
>>  Trees: local/main stable/main
>> ---
>> Lanny Ripple
>> [email protected]
>> 
>> 
>> 
>> 
>> 
> 
> I'm not sure exactly what "Git uses the sed found on the PATH in git-am"
> means.  This is a general list, not focused specifically on git and/or
> sed.
> 
> If you mean that git builds and runs differently depending on whether
> Apple's (BSD) sed or Fink's (GNU) sed is the first one in the PATH, then
> the maintainer (cc'ed) potentially should do something to fix that.
> 
> If, on the other hand, you mean that git only _runs_ differently
> depending on which sed is the first in the PATH, that's a different
> matter.  It may be the case that there's something that needs to be
> fixed by our sed maintainer (also cc'ed).
> 
> Or there may be nothing for us to do other than put a note in the usage
> section of git's package description.  Our sed and the built-in sed
> _are_ different, but it's probably excessive to forbid people to install
> Fink's sed just because they have git.
> 
> -- 
> Alexander Hansen, Ph.D.
> Fink User Liaison
> http://finkakh.wordpress.com/2012/02/21/got-job/

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to