Making progress, but stuck on nokogiri; any ideas? Wondering if it's
some problem with OS X and brew?

Installing nokogiri (1.5.5) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
extension.

/usr/local/Cellar/ruby/1.9.2-p180/bin/ruby extconf.rb
checking for libxml/parser.h... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.

On Wed, Jul 18, 2012 at 10:39 AM, Bruce D'Arcus <[email protected]> wrote:
> I don't know, is it just that the '-t' here should be a '-b'?
>
> $ git checkout -t origin/development
>
> On Wed, Jul 18, 2012 at 10:37 AM, Bruce D'Arcus <[email protected]> wrote:
>> There's one little detail you're missing on the instructions. By
>> default, git won't pull in remote branches (like "development"). So
>> you need to add the command to do that (which I forget).
>>
>> On Wed, Jul 18, 2012 at 4:04 AM, Sylvester Keil <[email protected]> wrote:
>>> I've added a wiki page with installation instructions here:
>>>
>>> https://github.com/citation-style-language/styles/wiki/Test-Environment
>>>
>>> Please let me know if anything is missing or unclear.
>>>
>>> Sylvester
>>>
>>>
>>> On Jul 17, 2012, at 6:07 PM, Charles Parnot wrote:
>>>
>>>> @sylvester: thanks! and 'development' seems like a good name :-)
>>>>
>>>> @bruce: thanks for the trip back to memory lane; had not thought of svn in 
>>>> a while… Given the nature of the CSL repo, and the low granularity, and 
>>>> given that there are almost no dependencies between files, it works very 
>>>> well to have just one shared branch, but I agree it's good to keep in mind.
>>>>
>>>> In fact, it reminds me of the discussion about CSL 1.0.1. With these tests 
>>>> put in place (and after giving it a bit of time to settle), maybe it would 
>>>> be nice to start thinking about that transition also in terms of branches. 
>>>> I know you had proposed to create a separate directory for the different 
>>>> version (how svn-like!!!), but a branch would likely work as well. Merging 
>>>> changes from development back into a 1.0.1 branch would allow to keep the 
>>>> 1.0.1 styles in sync, and eventually, the 'development' branch could be 
>>>> split to leave a 1.0.0 branch behind, and switch its content to 1.0.1 
>>>> styles. At that point, 'master' would pick up those 1.0.1 styles as well. 
>>>> The 1.0.0 branch could also be updated by merging back 'master' into it 
>>>> (but being careful to then strip the changes that are 1.0.1 specific).
>>>>
>>>>
>>>>
>>>> On Jul 17, 2012, at 8:53 AM, Bruce D'Arcus wrote:
>>>>
>>>>> One thing to keep in mind about git: branches are super lightweight.
>>>>> So, for example, it's possible to consider dev branches for every
>>>>> committer.
>>>>>
>>>>> I'm not saying this is a great idea; just suggesting you all not be
>>>>> bound by CVS/SVN thinking on branches.
>>>>>
>>>>> On Tue, Jul 17, 2012 at 11:43 AM, Rintze Zelle <[email protected]> 
>>>>> wrote:
>>>>>> "development" is fine.
>>>>>>
>>>>>> Rintze
>>>>>>
>>>>>> On Tue, Jul 17, 2012 at 11:13 AM, Sylvester Keil <[email protected]>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Jul 17, 2012, at 4:07 PM, Rintze Zelle wrote:
>>>>>>>
>>>>>>>> Yes, keeping the master branch of
>>>>>>>> https://github.com/citation-style-language/styles as the canonical one 
>>>>>>>> makes
>>>>>>>> sense.
>>>>>>>>
>>>>>>>> So the consensus seems to be that a new branch for untested test should
>>>>>>>> suffice? I'd be very happy if one of you could pick up the gauntlet 
>>>>>>>> and set
>>>>>>>> this up (I prefer to hide behind the excuse that I'm not a professional
>>>>>>>> programmer). I can give read/write access to the repo to anybody 
>>>>>>>> interested.
>>>>>>>
>>>>>>> I'll gladly create the new branch and set up the test-environment there.
>>>>>>> Any preferences for the branch name? (I would have suggested 
>>>>>>> 'development'
>>>>>>> or 'dev' myself)
>>>>>>>
>>>>>>> Sylvester
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> 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/
>>>>>>> _______________________________________________
>>>>>>> xbiblio-devel mailing list
>>>>>>> [email protected]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> 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/
>>>>>> _______________________________________________
>>>>>> xbiblio-devel mailing list
>>>>>> [email protected]
>>>>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> 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/
>>>>> _______________________________________________
>>>>> xbiblio-devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>>>>
>>>> --
>>>> Charles Parnot
>>>> [email protected]
>>>> twitter: @cparnot
>>>> http://mekentosj.com
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> 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/
>>>> _______________________________________________
>>>> xbiblio-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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/
>>> _______________________________________________
>>> xbiblio-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>>>

------------------------------------------------------------------------------
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/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

Reply via email to