nokogiri 1.0.0 → 1.6.8.1

data/Y_U_NO_GEMSPEC.md

@@ -0,0 +1,155 @@
+(note: this was originally a blog post published at http://blog.flavorjon.es/2012/03/y-u-no-gemspec.html)
+
+## tl;dr
+
+1. Team Nokogiri are not 10-foot-tall code-crunching robots, so `master` is usually unstable.
+2. Unstable code can corrupt your data and crash your application, which would make everybody look bad.
+3. Therefore, the _risk_ associated with using unstable code is severe; for you _and_ for Team Nokogiri.
+4. The absence of a gemspec is a risk mitigation tactic.
+5. You can always ask for an RC release.
+
+
+## Why Isn't There a Gemspec!?
+
+OHAI! Thank you for asking this question!
+
+Team Nokogiri gets asked this pretty frequently. Just a sample from
+the historical record:
+
+* [Issue #274](https://github.com/sparklemotion/nokogiri/issues/274)
+* [Issue #371](https://github.com/sparklemotion/nokogiri/issues/371)
+* [A commit removing nokogiri.gemspec](https://github.com/sparklemotion/nokogiri/commit/7f17a643a05ca381d65131515b54d4a3a61ca2e1#commitcomment-667477)
+* [A nokogiri-talk thread](http://groups.google.com/group/nokogiri-talk/browse_thread/thread/4706b002e492d23f)
+* [Another nokogiri-talk thread](http://groups.google.com/group/nokogiri-talk/browse_thread/thread/0b201bb80ea3eea0)
+
+Sometimes people imply that we've forgotten, or that we don't how to
+properly manage our codebase. Those people are super fun to respond
+to!
+
+We've gone back and forth a couple of times over the past few years,
+but the current policy of Team Nokogiri is to **not** provide a
+gemspec in the Github repo. This is a conscious choice, not an
+oversight.
+
+
+## But You Didn't Answer the Question!
+
+Ah, I was hoping you wouldn't notice. Well, OK, let's do this, if
+you're serious about it.
+
+I'd like to start by talking about _risk_. Specifically, the risk
+associated with using a known-unstable version of Nokogiri.
+
+
+### Risk
+
+One common way to evaluate the _risk_ of an incident is:
+
+    risk = probability x impact
+
+You can read more about this on [the internets](http://en.wikipedia.org/wiki/Risk_Matrix).
+
+The _risk_ associated with a Nokogiri bug could be loosely defined by
+answering the questions:
+
+* "How likely is it that a bug exists?" (probability)
+* "How severe will the consequences of a bug be?" (impact)
+
+
+### Probability
+
+The `master` branch should be considered unstable. Team Nokogiri are
+not 10-foot-tall code-crunching robots; we are humans. We make
+mistakes, and as a result, any arbitrary commit on `master` is likely
+to contain bugs.
+
+Just as an example, Nokogiri `master` was unstable for about five
+months between November 2011 and March 2012. It was unstable not
+because we were sloppy, or didn't care, but because the fixes were
+hard and unobvious.
+
+When we release Nokogiri, we test for memory leaks and invalid memory
+access on all kinds of platforms with many flavors of Ruby and lots of
+versions of libxml2. Because these tests are time-consuming, we don't
+run them on every commit. We run them often when preparing a release.
+
+If we're releasing Nokogiri, it means we think it's rock solid.
+
+And if we're not releasing it, it means there are probably bugs.
+
+
+### Impact
+
+Nokogiri is a gem with native extensions. This means it's not pure
+Ruby -- there's C or Java code being compiled and run, which means
+that there's always a chance that the gem will crash your application,
+or worse. Possible outcomes include:
+
+* leaking memory
+* corrupting data
+* making benign code crash (due to memory corruption)
+
+So, then, a bug in a native extension can have much worse downside
+than you might think. It's not just going to do something unexpected;
+it's possibly going to do terrible, awful things to your application
+and data.
+
+**Nobody** wants that to happen. Especially Team Nokogiri.
+
+
+### Risk, Redux
+
+So, if you accept the equation
+
+    risk = probability x impact
+
+and you believe me when I say that:
+
+* the probablility of a bug in unreleased code is high, and
+* the impact of a bug is likely to be severe,
+
+then you should easily see that the _risk_ associated with a bug in
+Nokogiri is quite high.
+
+Part of Team Nokogiri's job is to try to mitigate this risk. We have a
+number of tactics that we use to accomplish this:
+
+* we respond quickly to bug reports, particularly when they are possible memory issues
+* we review each others' commits
+* we have a thorough test suite, and we test-drive new features
+* we discuss code design and issues on a core developer mailing list
+* we use valgrind to test for memory issues (leaks and invalid
+  access) on multiple combinations of OS, libxml2 and Ruby
+* we package release candidates, and encourage devs to use them
+* **we do NOT commit a gemspec in our git repository**
+
+Yes, that's right, the absence of a gemspec is a risk mitigation
+tactic. Not only does Team Nokogiri not want to imply support for
+`master`, we want to **actively discourage** people from using
+it. Because it's not stable.
+
+
+## But I Want to Do It Anyway
+
+Another option, is to email the [nokogiri-talk
+list](http://groups.google.com/group/nokogiri-talk) and ask for a
+release candidate to be built. We're pretty accommodating if there's a
+bugfix that's a blocker for you. And if we can't release an RC, we'll
+tell you why.
+
+And in the end, nothing is stopping you from cloning the repo and
+generating a private gemspec. This is an extra step or two, but it has
+the benefit of making sure developers have thought through the costs
+and risks involved; and it tends to select for developers who know
+what they're doing.
+
+
+## In Conclusion
+
+Team Nokogiri takes stability very seriously. We want everybody who
+uses Nokogiri to have a pleasant experience. And so we want to make
+sure that you're using the best software we can make.
+
+Please keep in mind that we're trying very hard to do the right thing
+for all Nokogiri users out there in Rubyland. Nokogiri loves you very
+much, and we hope you love it back.

data/appveyor.yml

@@ -0,0 +1,22 @@
+install:
+  - SET PATH=C:\Ruby%ruby_version%\bin;%PATH%
+  - SET PATH=C:\MinGW\bin;%PATH%
+  - SET RAKEOPT=-rdevkit
+  - ruby --version
+  - gem --version
+  - bundle install
+
+build: off
+
+test_script:
+  - bundle exec rake
+
+environment:
+  matrix:
+    - ruby_version: "22"
+    - ruby_version: "22-x64"
+    - ruby_version: "21"
+    - ruby_version: "21-x64"
+    - ruby_version: "200"
+    - ruby_version: "200-x64"
+    - ruby_version: "193"

data/bin/nokogiri

@@ -0,0 +1,118 @@
+#!/usr/bin/env ruby
+require 'optparse'
+require 'open-uri'
+require 'uri'
+require 'rubygems'
+require 'nokogiri'
+autoload :IRB, 'irb'
+
+parse_class = Nokogiri
+encoding = nil
+
+# This module provides some tunables with the nokogiri CLI for use in
+# your ~/.nokogirirc.
+module Nokogiri::CLI
+  class << self
+    # Specify the console engine, defaulted to IRB.
+    #
+    # call-seq:
+    #   require 'pry'
+    #   Nokogiri::CLI.console = Pry
+    attr_writer :console
+
+    def console
+      case @console
+      when Symbol
+        Kernel.const_get(@console)
+      else
+        @console
+      end
+    end
+
+    attr_accessor :rcfile
+  end
+
+  self.rcfile  = File.expand_path('~/.nokogirirc')
+  self.console = :IRB
+end
+
+opts = OptionParser.new do |opts|
+  opts.banner = "Nokogiri: an HTML, XML, SAX, and Reader parser"
+  opts.define_head "Usage: nokogiri <uri|path> [options]"
+  opts.separator ""
+  opts.separator "Examples:"
+  opts.separator "  nokogiri https://www.ruby-lang.org/"
+  opts.separator "  nokogiri ./public/index.html"
+  opts.separator "  curl -s http://www.nokogiri.org | nokogiri -e'p $_.css(\"h1\").length'"
+  opts.separator ""
+  opts.separator "Options:"
+
+  opts.on("--type type", "Parse as type: xml or html (default: auto)", [:xml, :html]) do |v|
+    parse_class = {:xml => Nokogiri::XML, :html => Nokogiri::HTML}[v]
+  end
+
+  opts.on("-C file", "Specifies initialization file to load (default #{Nokogiri::CLI.rcfile})") do |v|
+    Nokogiri::CLI.rcfile = v
+  end
+
+  opts.on("-E", "--encoding encoding", "Read as encoding (default: #{encoding || 'none'})") do |v|
+    encoding = v
+  end
+
+  opts.on("-e command", "Specifies script from command-line.") do |v|
+    @script = v
+  end
+
+  opts.on("--rng <uri|path>", "Validate using this rng file.") do |v|
+    @rng = open(v) {|f| Nokogiri::XML::RelaxNG(f)}
+  end
+
+  opts.on_tail("-?", "--help", "Show this message") do
+    puts opts
+    exit
+  end
+
+  opts.on_tail("-v", "--version", "Show version") do
+    puts Nokogiri::VersionInfo.instance.to_markdown
+    exit
+  end
+end
+opts.parse!
+
+url = ARGV.shift
+
+if url.to_s.strip.empty? && $stdin.tty?
+  puts opts
+  exit 1
+end
+
+if File.file?(Nokogiri::CLI.rcfile)
+  load Nokogiri::CLI.rcfile
+end
+
+if url || $stdin.tty?
+  case uri = (URI(url) rescue url)
+  when URI::HTTP
+    @doc = parse_class.parse(uri.read, url, encoding)
+  else
+    @doc = parse_class.parse(open(url).read, nil, encoding)
+  end
+else
+  @doc = parse_class.parse($stdin, nil, encoding)
+end
+
+$_ = @doc
+
+if @rng
+  @rng.validate(@doc).each do |error|
+    puts error.message
+  end
+else
+  if @script
+    eval @script, binding, '<main>'
+  else
+    puts "Your document is stored in @doc..."
+    Nokogiri::CLI.console.start
+  end
+end
+

data/build_all

@@ -0,0 +1,45 @@
+#! /usr/bin/env bash
+#
+#  script to build gems for all relevant platforms:
+#  - MRI et al (standard gem)
+#  - windows (x86-mingw32 and x64-mingw32)
+#  - jruby
+#
+
+# Load RVM into a shell session *as a function*
+if [[ -s "$HOME/.rvm/scripts/rvm" ]] ; then
+    source "$HOME/.rvm/scripts/rvm"
+elif [[ -s "/usr/local/rvm/scripts/rvm" ]] ; then
+    source "/usr/local/rvm/scripts/rvm"
+else
+    echo "ERROR: An RVM installation was not found.\n"
+fi
+
+set -o errexit
+#set -x
+
+rm -rf tmp pkg
+bundle exec rake clean clobber
+
+# holding pen
+rm -rf gems
+mkdir -p gems
+
+# windows
+bundle exec rake gem:windows
+cp -v pkg/nokogiri*{x86,x64}-mingw32*.gem gems
+
+# MRI
+bundle exec rake clean
+bundle exec rake gem
+cp -v pkg/nokogiri*.gem gems
+
+# jruby
+bundle exec rake clean clobber
+bundle exec rake generate
+
+rvm jruby-1.7.19
+gem install bundler --conservative
+bundle install --quiet --local || bundle install
+bundle exec rake gem
+cp -v pkg/nokogiri*java.gem gems

data/dependencies.yml

@@ -0,0 +1,29 @@
+libxml2:
+  version: "2.9.4"
+  md5: "ae249165c173b1ff386ee8ad676815f5" # manually confirmed via `gpg --verify`
+  # gpg: Signature made Mon 23 May 2016 04:02:13 AM EDT using DSA key ID DE95BC1F
+  # gpg: Good signature from "Daniel Veillard (Red Hat work email) <veillard@redhat.com>"
+  # gpg:                 aka "Daniel Veillard <Daniel.Veillard@w3.org>"
+  # gpg: WARNING: This key is not certified with a trusted signature!
+  # gpg:          There is no indication that the signature belongs to the owner.
+  # Primary key fingerprint: C744 15BA 7C9C 7F78 F02E  1DC3 4606 B8A5 DE95 BC1F
+
+libxslt:
+  version: "1.1.29"
+  md5: "a129d3c44c022de3b9dcf6d6f288d72e"
+  # gpg: Signature made Mon 23 May 2016 09:58:52 PM EDT using DSA key ID DE95BC1F
+  # gpg: Good signature from "Daniel Veillard (Red Hat work email) <veillard@redhat.com>"
+  # gpg:                 aka "Daniel Veillard <Daniel.Veillard@w3.org>"
+  # gpg: WARNING: This key is not certified with a trusted signature!
+  # gpg:          There is no indication that the signature belongs to the owner.
+  # Primary key fingerprint: C744 15BA 7C9C 7F78 F02E  1DC3 4606 B8A5 DE95 BC1F
+
+zlib:
+  version: "1.2.8"
+  md5: "44d667c142d7cda120332623eab69f40"
+
+libiconv:
+  version: "1.14"
+  md5: "e34509b1623cec449dfeb73d7ce9c6c6"
+  # gpg: Signature made Sun 07 Aug 2011 01:58:18 PM EDT using DSA key ID F059B1D1
+  # gpg: BAD signature from "Bruno Haible (Open Source Development) <bruno@clisp.org>"