Results for: "Dir.chdir"

Returns the size of uri in bytes.

Returns true when it is possible and safe to update the cache directory.

Fetches a specification for the given name_tuple.

Yields each source in the list.

Returns the full path to the cached gem for this spec.

Creates a duplicate spec without large blobs that aren’t used at runtime.

Reads a Marshal file at path

Creates a SpecFetcher pre-filled with the gems or specs defined in the block.

Yields a fetcher object that responds to spec and gem. spec adds a specification to the SpecFetcher while gem adds both a specification and the gem data to the RemoteFetcher so the built gem can be downloaded.

If only the a-3 gem is supposed to be downloaded you can save setup time by creating only specs for the other versions:

spec_fetcher do |fetcher|
  fetcher.spec 'a', 1
  fetcher.spec 'a', 2, 'b' => 3 # dependency on b = 3
  fetcher.gem 'a', 3 do |spec|
    # spec is a Gem::Specification
    # ...
  end
end

schedule a command

protected setter for the scheme component v

see also URI::Generic.scheme=

check the user and password.

If password is not provided, then user is split, using URI::Generic.split_userinfo, to pull user and +password.

see also URI::Generic.check_user, URI::Generic.check_password

check the user v component for RFC2396 compliance and against the URI::Parser Regexp for :USERINFO

Can not have a registry or opaque component defined, with a user component defined.

check the password v component for RFC2396 compliance and against the URI::Parser Regexp for :USERINFO

Can not have a registry or opaque component defined, with a user component defined.

check the host v component for RFC2396 compliance and against the URI::Parser Regexp for :HOST

Can not have a registry or opaque component defined, with a host component defined.

check the port v component for RFC2396 compliance and against the URI::Parser Regexp for :PORT

Can not have a registry or opaque component defined, with a port component defined.

check the path v component for RFC2396 compliance and against the URI::Parser Regexp for :ABS_PATH and :REL_PATH

Can not have a opaque component defined, with a path component defined.

check the opaque v component for RFC2396 compliance and against the URI::Parser Regexp for :OPAQUE

Can not have a host, port, user or path component defined, with an opaque component defined.

check the to v component

check the headers v component against either

• HEADER_REGEXP