Nokogiri

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Nokogiri

LightGuard
Administrator
We're currently using Nokogiri in three places:

* lib/awestruct/handlers/restructuredtext_handler.rb
* lib/awestruct/context_helper.rb
* lib/awestruct/extensions/coffeescripttransform.rb

The context_helper.rb file make use of it in one function, which is called from lib/awestruct/extensions/template.atom.haml. 

We've already agreed we're okay dropping the RST (restructured text) handler. The other two are a bit harder to figure out. I mentioned the context_helper. That could be pulled out into awepress. The coffeescripttransform can be handled by haml and slim, so we're probably good to take it out. I'd like to hear people's thoughts before I make changes.
Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

Emmanuel Bernard
Are you saying that I would need to somehow migrate blog sites from Awestruct to awepress to get a proper atom feed?
A feed generator is quite core to what Awestruct offer IMO.

> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]> wrote:
>
> We're currently using Nokogiri in three places:
>
> * lib/awestruct/handlers/restructuredtext_handler.rb
> * lib/awestruct/context_helper.rb
> * lib/awestruct/extensions/coffeescripttransform.rb
>
> The context_helper.rb file make use of it in one function, which is called from lib/awestruct/extensions/template.atom.haml.
>
> We've already agreed we're okay dropping the RST (restructured text) handler. The other two are a bit harder to figure out. I mentioned the context_helper. That could be pulled out into awepress. The coffeescripttransform can be handled by haml and slim, so we're probably good to take it out. I'd like to hear people's thoughts before I make changes.

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

Torsten Curdt
I agree with Emmanuel. Atom feeds are a core part. Not sure why we
would try so hard to drop Nokigiri when we just added asciidoc. That
doesn't add up to me.

On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
<[hidden email]> wrote:

> Are you saying that I would need to somehow migrate blog sites from Awestruct to awepress to get a proper atom feed?
> A feed generator is quite core to what Awestruct offer IMO.
>
>> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]> wrote:
>>
>> We're currently using Nokogiri in three places:
>>
>> * lib/awestruct/handlers/restructuredtext_handler.rb
>> * lib/awestruct/context_helper.rb
>> * lib/awestruct/extensions/coffeescripttransform.rb
>>
>> The context_helper.rb file make use of it in one function, which is called from lib/awestruct/extensions/template.atom.haml.
>>
>> We've already agreed we're okay dropping the RST (restructured text) handler. The other two are a bit harder to figure out. I mentioned the context_helper. That could be pulled out into awepress. The coffeescripttransform can be handled by haml and slim, so we're probably good to take it out. I'd like to hear people's thoughts before I make changes.
>
> ---------------------------------------------------------------------
> Archives: http://talk-archive.awestruct.org/
> To unsubscribe, e-mail: [hidden email]
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

LightGuard
Administrator
Awepress, just like aweplug is (will be) a  collection of extensions, helpers and utilities focused on writing blogs. The main idea of splitting things out is to make awestruct simply a rendering tool chain. 

If we don't like to idea, that's fine. The reason I'm looking at removing Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults, but if you're both running on 1.9.3 and not seeing issues I can dig deeper. 

Sent from Mailbox for iPhone


On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:

I agree with Emmanuel. Atom feeds are a core part. Not sure why we
would try so hard to drop Nokigiri when we just added asciidoc. That
doesn't add up to me.

On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
<[hidden email]> wrote:


> Are you saying that I would need to somehow migrate blog sites from Awestruct to awepress to get a proper atom feed?
> A feed generator is quite core to what Awestruct offer IMO.
>
>> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]> wrote:
>>
>> We're currently using Nokogiri in three places:
>>
>> * lib/awestruct/handlers/restructuredtext_handler.rb
>> * lib/awestruct/context_helper.rb
>> * lib/awestruct/extensions/coffeescripttransform.rb
>>
>> The context_helper.rb file make use of it in one function, which is called from lib/awestruct/extensions/template.atom.haml.
>>
>> We've already agreed we're okay dropping the RST (restructured text) handler. The other two are a bit harder to figure out. I mentioned the context_helper. That could be pulled out into awepress. The coffeescripttransform can be handled by haml and slim, so we're probably good to take it out. I'd like to hear people's thoughts before I make changes.
>
> ---------------------------------------------------------------------
> Archives: http://talk-archive.awestruct.org/
> To unsubscribe, e-mail: [hidden email]
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

Torsten Curdt
I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.

On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:

> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

LightGuard
Administrator
Doing some more digging (and I need some feedback from those who opened segfault bugs) it looks like nokogiri may be a problem depending on which version of libxml it's compiled against. If that's the case, there really isn't much we can do about it, and actually it isn't our bug.


On Tue, Apr 22, 2014 at 7:37 AM, Torsten Curdt <[hidden email]> wrote:
I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.

On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:
> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]




--
Reply | Threaded
Open this post in threaded view
|

RE: Nokogiri

vdanilchenko@vistaprint.com

I have had some problems with  Nokogiri because it has very version-specific dependencies on the system libxml package version, apparently… an OS upgrade changed the libxml version and Nokogiri stopped compiling normally – any ‘gem install’ would throw errors. I did track them down, but it was a pain.

 

I didn’t write down the details (should have), but Nokogiri was the only gem that gave me problems.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, April 22, 2014 1:45 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Doing some more digging (and I need some feedback from those who opened segfault bugs) it looks like nokogiri may be a problem depending on which version of libxml it's compiled against. If that's the case, there really isn't much we can do about it, and actually it isn't our bug.

 

On Tue, Apr 22, 2014 at 7:37 AM, Torsten Curdt <[hidden email]> wrote:

I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.


On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:
> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]



 

--

Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

LightGuard
Administrator
Yep, Nokogiri is not a fun one. We're still talking on the list (as you may have seen) about what to do with it. I can tell you for sure though, if you're running on ruby 1.9.3 (or lower) you will have many more problems. I strongly suggest people upgrade to at least 2.0.0, 2.1.1 if you can.


On Tue, Apr 29, 2014 at 10:53 AM, Victor Danilchenko <[hidden email]> wrote:

I have had some problems with  Nokogiri because it has very version-specific dependencies on the system libxml package version, apparently… an OS upgrade changed the libxml version and Nokogiri stopped compiling normally – any ‘gem install’ would throw errors. I did track them down, but it was a pain.

 

I didn’t write down the details (should have), but Nokogiri was the only gem that gave me problems.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, April 22, 2014 1:45 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Doing some more digging (and I need some feedback from those who opened segfault bugs) it looks like nokogiri may be a problem depending on which version of libxml it's compiled against. If that's the case, there really isn't much we can do about it, and actually it isn't our bug.

 

On Tue, Apr 22, 2014 at 7:37 AM, Torsten Curdt <[hidden email]> wrote:

I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.


On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:
> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]



 

--




--
Reply | Threaded
Open this post in threaded view
|

RE: Nokogiri

vdanilchenko@vistaprint.com

Yes, I am running on 1.9.3 – and thanks, I will upgrade to 2.0.

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, April 29, 2014 12:55 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Yep, Nokogiri is not a fun one. We're still talking on the list (as you may have seen) about what to do with it. I can tell you for sure though, if you're running on ruby 1.9.3 (or lower) you will have many more problems. I strongly suggest people upgrade to at least 2.0.0, 2.1.1 if you can.

 

On Tue, Apr 29, 2014 at 10:53 AM, Victor Danilchenko <[hidden email]> wrote:

I have had some problems with  Nokogiri because it has very version-specific dependencies on the system libxml package version, apparently… an OS upgrade changed the libxml version and Nokogiri stopped compiling normally – any ‘gem install’ would throw errors. I did track them down, but it was a pain.

 

I didn’t write down the details (should have), but Nokogiri was the only gem that gave me problems.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, April 22, 2014 1:45 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Doing some more digging (and I need some feedback from those who opened segfault bugs) it looks like nokogiri may be a problem depending on which version of libxml it's compiled against. If that's the case, there really isn't much we can do about it, and actually it isn't our bug.

 

On Tue, Apr 22, 2014 at 7:37 AM, Torsten Curdt <[hidden email]> wrote:

I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.


On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:
> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]



 

--



 

--

Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

ge0ffrey
From a user's POV:

Nokogiri is a PITA in during awestruct installation on linux (or at least it was).
Unlike other dependencies (gems) that are automatically provided, nokogiri wasn't.
So getting rid of it, making the already complex installation easier, is a good thing.

But atom should still work too... :)

On 29-04-14 20:05, Victor Danilchenko wrote:

Yes, I am running on 1.9.3 – and thanks, I will upgrade to 2.0.

 

From: Jason Porter [[hidden email]]
Sent: Tuesday, April 29, 2014 12:55 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Yep, Nokogiri is not a fun one. We're still talking on the list (as you may have seen) about what to do with it. I can tell you for sure though, if you're running on ruby 1.9.3 (or lower) you will have many more problems. I strongly suggest people upgrade to at least 2.0.0, 2.1.1 if you can.

 

On Tue, Apr 29, 2014 at 10:53 AM, Victor Danilchenko <[hidden email]> wrote:

I have had some problems with  Nokogiri because it has very version-specific dependencies on the system libxml package version, apparently… an OS upgrade changed the libxml version and Nokogiri stopped compiling normally – any ‘gem install’ would throw errors. I did track them down, but it was a pain.

 

I didn’t write down the details (should have), but Nokogiri was the only gem that gave me problems.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, April 22, 2014 1:45 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Doing some more digging (and I need some feedback from those who opened segfault bugs) it looks like nokogiri may be a problem depending on which version of libxml it's compiled against. If that's the case, there really isn't much we can do about it, and actually it isn't our bug.

 

On Tue, Apr 22, 2014 at 7:37 AM, Torsten Curdt <[hidden email]> wrote:

I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.


On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:
> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]



 

--



 

--


Reply | Threaded
Open this post in threaded view
|

Re: Nokogiri

LightGuard
Administrator
It used to be bad, it isn't anymore, thankfully. 

Sent from Mailbox


On Thu, Jun 12, 2014 at 5:52 AM, Geoffrey De Smet <[hidden email]> wrote:

From a user's POV:

Nokogiri is a PITA in during awestruct installation on linux (or at least it was).
Unlike other dependencies (gems) that are automatically provided, nokogiri wasn't.
So getting rid of it, making the already complex installation easier, is a good thing.

But atom should still work too... :)

On 29-04-14 20:05, Victor Danilchenko wrote:

Yes, I am running on 1.9.3 – and thanks, I will upgrade to 2.0.

 

From: Jason Porter [[hidden email]]
Sent: Tuesday, April 29, 2014 12:55 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Yep, Nokogiri is not a fun one. We're still talking on the list (as you may have seen) about what to do with it. I can tell you for sure though, if you're running on ruby 1.9.3 (or lower) you will have many more problems. I strongly suggest people upgrade to at least 2.0.0, 2.1.1 if you can.

 

On Tue, Apr 29, 2014 at 10:53 AM, Victor Danilchenko <[hidden email]> wrote:

I have had some problems with  Nokogiri because it has very version-specific dependencies on the system libxml package version, apparently… an OS upgrade changed the libxml version and Nokogiri stopped compiling normally – any ‘gem install’ would throw errors. I did track them down, but it was a pain.

 

I didn’t write down the details (should have), but Nokogiri was the only gem that gave me problems.

 

 

From: Jason Porter [mailto:[hidden email]]
Sent: Tuesday, April 22, 2014 1:45 PM
To: [hidden email]
Subject: Re: [awestruct] Nokogiri

 

Doing some more digging (and I need some feedback from those who opened segfault bugs) it looks like nokogiri may be a problem depending on which version of libxml it's compiled against. If that's the case, there really isn't much we can do about it, and actually it isn't our bug.

 

On Tue, Apr 22, 2014 at 7:37 AM, Torsten Curdt <[hidden email]> wrote:

I was on 1.9.3 until about last week. Never had problems with it.

In general I am fine to keep the core slim but it's not like awestruct
is a kitchen sink yet.
And if you want to strip it down - atom feels much more core than e.g.
the compass stuff.


On Tue, Apr 22, 2014 at 3:16 PM, Jason Porter <[hidden email]> wrote:
> Awepress, just like aweplug is (will be) a  collection of extensions,
> helpers and utilities focused on writing blogs. The main idea of splitting
> things out is to make awestruct simply a rendering tool chain.
>
> If we don't like to idea, that's fine. The reason I'm looking at removing
> Nokogiri  is to make things work on 1.9.3. I believe it's causing segfaults,
> but if you're both running on 1.9.3 and not seeing issues I can dig deeper.
> —
> Sent from Mailbox for iPhone
>
>
> On Tue, Apr 22, 2014 at 1:21 AM, Torsten Curdt <[hidden email]> wrote:
>>
>> I agree with Emmanuel. Atom feeds are a core part. Not sure why we
>> would try so hard to drop Nokigiri when we just added asciidoc. That
>> doesn't add up to me.
>>
>> On Tue, Apr 22, 2014 at 9:05 AM, Emmanuel Bernard
>> <[hidden email]> wrote:
>> > Are you saying that I would need to somehow migrate blog sites from
>> > Awestruct to awepress to get a proper atom feed?
>> > A feed generator is quite core to what Awestruct offer IMO.
>> >
>> >> On 22 avr. 2014, at 05:44, Jason Porter <[hidden email]>
>> >> wrote:
>> >>
>> >> We're currently using Nokogiri in three places:
>> >>
>> >> * lib/awestruct/handlers/restructuredtext_handler.rb
>> >> * lib/awestruct/context_helper.rb
>> >> * lib/awestruct/extensions/coffeescripttransform.rb
>> >>
>> >> The context_helper.rb file make use of it in one function, which is
>> >> called from lib/awestruct/extensions/template.atom.haml.
>> >>
>> >> We've already agreed we're okay dropping the RST (restructured text)
>> >> handler. The other two are a bit harder to figure out. I mentioned the
>> >> context_helper. That could be pulled out into awepress. The
>> >> coffeescripttransform can be handled by haml and slim, so we're probably
>> >> good to take it out. I'd like to hear people's thoughts before I make
>> >> changes.
>> >
>> > ---------------------------------------------------------------------
>> > Archives: http://talk-archive.awestruct.org/
>> > To unsubscribe, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> Archives: http://talk-archive.awestruct.org/
>> To unsubscribe, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]



 

--



 

--