2024-06-02 15:14:25 +01:00
|
|
|
# typed: strict
|
2020-08-08 07:16:06 +05:30
|
|
|
# frozen_string_literal: true
|
|
|
|
|
2025-03-04 11:48:54 -08:00
|
|
|
require "livecheck/strategic"
|
|
|
|
|
2020-08-08 07:16:06 +05:30
|
|
|
module Homebrew
|
|
|
|
module Livecheck
|
|
|
|
module Strategy
|
2020-11-05 17:17:03 -05:00
|
|
|
# The {Gnome} strategy identifies versions of software at gnome.org by
|
2020-08-08 07:16:06 +05:30
|
|
|
# checking the available downloads found in a project's `cache.json`
|
|
|
|
# file.
|
|
|
|
#
|
2020-11-05 17:17:03 -05:00
|
|
|
# GNOME URLs generally follow a standard format:
|
|
|
|
#
|
|
|
|
# * `https://download.gnome.org/sources/example/1.2/example-1.2.3.tar.xz`
|
2020-08-08 07:16:06 +05:30
|
|
|
#
|
2021-05-31 19:47:08 +05:30
|
|
|
# Before version 40, GNOME used a version scheme where unstable releases
|
|
|
|
# were indicated with a minor that's 90+ or odd. The newer version scheme
|
|
|
|
# uses trailing alpha/beta/rc text to identify unstable versions
|
2023-09-08 14:46:15 -04:00
|
|
|
# (e.g. `40.alpha`).
|
2021-05-30 21:53:17 +05:30
|
|
|
#
|
2021-05-31 19:47:08 +05:30
|
|
|
# When a regex isn't provided in a `livecheck` block, the strategy uses
|
|
|
|
# a default regex that matches versions which don't include trailing text
|
2023-09-08 14:46:15 -04:00
|
|
|
# after the numeric version (e.g. `40.0` instead of `40.alpha`) and it
|
2021-05-31 19:47:08 +05:30
|
|
|
# selectively filters out unstable versions below 40 using the rules for
|
|
|
|
# the older version scheme.
|
2020-08-08 07:16:06 +05:30
|
|
|
#
|
|
|
|
# @api public
|
|
|
|
class Gnome
|
2025-02-22 21:51:41 -08:00
|
|
|
extend Strategic
|
|
|
|
|
2020-08-08 07:16:06 +05:30
|
|
|
NICE_NAME = "GNOME"
|
|
|
|
|
|
|
|
# The `Regexp` used to determine if the strategy applies to the URL.
|
2020-12-21 00:48:31 -05:00
|
|
|
URL_MATCH_REGEX = %r{
|
|
|
|
^https?://download\.gnome\.org
|
|
|
|
/sources
|
|
|
|
/(?<package_name>[^/]+)/ # The GNOME package name
|
2024-01-18 22:18:42 +00:00
|
|
|
}ix
|
2020-08-08 07:16:06 +05:30
|
|
|
|
|
|
|
# Whether the strategy can be applied to the provided URL.
|
2020-11-05 17:17:03 -05:00
|
|
|
#
|
2020-08-08 07:16:06 +05:30
|
|
|
# @param url [String] the URL to match against
|
|
|
|
# @return [Boolean]
|
2025-02-22 21:51:41 -08:00
|
|
|
sig { override.params(url: String).returns(T::Boolean) }
|
2020-08-08 07:16:06 +05:30
|
|
|
def self.match?(url)
|
|
|
|
URL_MATCH_REGEX.match?(url)
|
|
|
|
end
|
|
|
|
|
2021-07-28 13:20:12 -04:00
|
|
|
# Extracts information from a provided URL and uses it to generate
|
|
|
|
# various input values used by the strategy to check for new versions.
|
|
|
|
# Some of these values act as defaults and can be overridden in a
|
|
|
|
# `livecheck` block.
|
|
|
|
#
|
|
|
|
# @param url [String] the URL used to generate values
|
|
|
|
# @return [Hash]
|
|
|
|
sig { params(url: String).returns(T::Hash[Symbol, T.untyped]) }
|
|
|
|
def self.generate_input_values(url)
|
|
|
|
values = {}
|
|
|
|
|
|
|
|
match = url.match(URL_MATCH_REGEX)
|
|
|
|
return values if match.blank?
|
|
|
|
|
|
|
|
values[:url] = "https://download.gnome.org/sources/#{match[:package_name]}/cache.json"
|
|
|
|
|
|
|
|
regex_name = Regexp.escape(T.must(match[:package_name])).gsub("\\-", "-")
|
|
|
|
|
|
|
|
# GNOME archive files seem to use a standard filename format, so we
|
|
|
|
# count on the delimiter between the package name and numeric
|
|
|
|
# version being a hyphen and the file being a tarball.
|
2022-06-10 19:07:05 -04:00
|
|
|
values[:regex] = /#{regex_name}-(\d+(?:\.\d+)*)\.t/i
|
2021-07-28 13:20:12 -04:00
|
|
|
|
|
|
|
values
|
|
|
|
end
|
|
|
|
|
2020-08-08 07:16:06 +05:30
|
|
|
# Generates a URL and regex (if one isn't provided) and passes them
|
2020-11-05 17:17:03 -05:00
|
|
|
# to {PageMatch.find_versions} to identify versions in the content.
|
|
|
|
#
|
2020-08-08 07:16:06 +05:30
|
|
|
# @param url [String] the URL of the content to check
|
|
|
|
# @param regex [Regexp] a regex used for matching versions in content
|
livecheck: Add Options class
This adds a `Livecheck::Options` class, which is intended to house
various configuration options that are set in `livecheck` blocks,
conditionally set by livecheck at runtime, etc. The general idea is
that when we add features involving configurations options (e.g., for
livecheck, strategies, curl, etc.), we can make changes to `Options`
without needing to modify parameters for strategy `find_versions`
methods, `Strategy` methods like `page_headers` and `page_content`,
etc. This is something that I've been trying to improve over the years
and `Options` should help to reduce maintenance overhead in this area
while also strengthening type signatures.
`Options` replaces the existing `homebrew_curl` option (which related
strategies pass to `Strategy` methods and on to `curl_args`) and the
new `url_options` (which contains `post_form` or `post_json` values
that are used to make `POST` requests). I recently added `url_options`
as a temporary way of enabling `POST` support without `Options` but
this restores the original `Options`-based implementation.
Along the way, I added a `homebrew_curl` parameter to the `url` DSL
method, allowing us to set an explicit value in `livecheck` blocks.
This is something that we've needed in some cases but I also intend
to replace implicit/inferred `homebrew_curl` usage with explicit
values in `livecheck` blocks once this is available for use. My
intention is to eventually remove the implicit behavior and only rely
on explicit values. That will align with how `homebrew_curl` options
work for other URLs and makes the behavior clear just from looking at
the `livecheck` block.
Lastly, this removes the `unused` rest parameter from `find_versions`
methods. I originally added `unused` as a way of handling parameters
that some `find_versions` methods have but others don't (e.g., `cask`
in `ExtractPlist`), as this allowed us to pass various arguments to
`find_versions` methods without worrying about whether a particular
parameter is available. This isn't an ideal solution and I originally
wanted to handle this situation by only passing expected arguments to
`find_versions` methods but there was a technical issue standing in
the way. I recently found an answer to the issue, so this also
replaces the existing `ExtractPlist` special case with generic logic
that checks the parameters for a strategy's `find_versions` method
and only passes expected arguments.
Replacing the aforementioned `find_versions` parameters with `Options`
ensures that the remaining parameters are fairly consistent across
strategies and any differences are handled by the aforementioned
logic. Outside of `ExtractPlist`, the only other difference is that
some `find_versions` methods have a `provided_content` parameter but
that's currently only used by tests (though it's intended for caching
support in the future). I will be renaming that parameter to `content`
in an upcoming PR and expanding it to the other strategies, which
should make them all consistent outside of `ExtractPlist`.
2025-02-11 18:04:38 -05:00
|
|
|
# @param options [Options] options to modify behavior
|
2020-08-08 07:16:06 +05:30
|
|
|
# @return [Hash]
|
2021-04-04 03:00:34 +02:00
|
|
|
sig {
|
2025-02-22 21:51:41 -08:00
|
|
|
override(allow_incompatible: true).params(
|
livecheck: Add Options class
This adds a `Livecheck::Options` class, which is intended to house
various configuration options that are set in `livecheck` blocks,
conditionally set by livecheck at runtime, etc. The general idea is
that when we add features involving configurations options (e.g., for
livecheck, strategies, curl, etc.), we can make changes to `Options`
without needing to modify parameters for strategy `find_versions`
methods, `Strategy` methods like `page_headers` and `page_content`,
etc. This is something that I've been trying to improve over the years
and `Options` should help to reduce maintenance overhead in this area
while also strengthening type signatures.
`Options` replaces the existing `homebrew_curl` option (which related
strategies pass to `Strategy` methods and on to `curl_args`) and the
new `url_options` (which contains `post_form` or `post_json` values
that are used to make `POST` requests). I recently added `url_options`
as a temporary way of enabling `POST` support without `Options` but
this restores the original `Options`-based implementation.
Along the way, I added a `homebrew_curl` parameter to the `url` DSL
method, allowing us to set an explicit value in `livecheck` blocks.
This is something that we've needed in some cases but I also intend
to replace implicit/inferred `homebrew_curl` usage with explicit
values in `livecheck` blocks once this is available for use. My
intention is to eventually remove the implicit behavior and only rely
on explicit values. That will align with how `homebrew_curl` options
work for other URLs and makes the behavior clear just from looking at
the `livecheck` block.
Lastly, this removes the `unused` rest parameter from `find_versions`
methods. I originally added `unused` as a way of handling parameters
that some `find_versions` methods have but others don't (e.g., `cask`
in `ExtractPlist`), as this allowed us to pass various arguments to
`find_versions` methods without worrying about whether a particular
parameter is available. This isn't an ideal solution and I originally
wanted to handle this situation by only passing expected arguments to
`find_versions` methods but there was a technical issue standing in
the way. I recently found an answer to the issue, so this also
replaces the existing `ExtractPlist` special case with generic logic
that checks the parameters for a strategy's `find_versions` method
and only passes expected arguments.
Replacing the aforementioned `find_versions` parameters with `Options`
ensures that the remaining parameters are fairly consistent across
strategies and any differences are handled by the aforementioned
logic. Outside of `ExtractPlist`, the only other difference is that
some `find_versions` methods have a `provided_content` parameter but
that's currently only used by tests (though it's intended for caching
support in the future). I will be renaming that parameter to `content`
in an upcoming PR and expanding it to the other strategies, which
should make them all consistent outside of `ExtractPlist`.
2025-02-11 18:04:38 -05:00
|
|
|
url: String,
|
|
|
|
regex: T.nilable(Regexp),
|
|
|
|
options: Options,
|
|
|
|
block: T.nilable(Proc),
|
2025-02-22 21:51:41 -08:00
|
|
|
).returns(T::Hash[Symbol, T.anything])
|
2021-04-04 03:00:34 +02:00
|
|
|
}
|
livecheck: Add Options class
This adds a `Livecheck::Options` class, which is intended to house
various configuration options that are set in `livecheck` blocks,
conditionally set by livecheck at runtime, etc. The general idea is
that when we add features involving configurations options (e.g., for
livecheck, strategies, curl, etc.), we can make changes to `Options`
without needing to modify parameters for strategy `find_versions`
methods, `Strategy` methods like `page_headers` and `page_content`,
etc. This is something that I've been trying to improve over the years
and `Options` should help to reduce maintenance overhead in this area
while also strengthening type signatures.
`Options` replaces the existing `homebrew_curl` option (which related
strategies pass to `Strategy` methods and on to `curl_args`) and the
new `url_options` (which contains `post_form` or `post_json` values
that are used to make `POST` requests). I recently added `url_options`
as a temporary way of enabling `POST` support without `Options` but
this restores the original `Options`-based implementation.
Along the way, I added a `homebrew_curl` parameter to the `url` DSL
method, allowing us to set an explicit value in `livecheck` blocks.
This is something that we've needed in some cases but I also intend
to replace implicit/inferred `homebrew_curl` usage with explicit
values in `livecheck` blocks once this is available for use. My
intention is to eventually remove the implicit behavior and only rely
on explicit values. That will align with how `homebrew_curl` options
work for other URLs and makes the behavior clear just from looking at
the `livecheck` block.
Lastly, this removes the `unused` rest parameter from `find_versions`
methods. I originally added `unused` as a way of handling parameters
that some `find_versions` methods have but others don't (e.g., `cask`
in `ExtractPlist`), as this allowed us to pass various arguments to
`find_versions` methods without worrying about whether a particular
parameter is available. This isn't an ideal solution and I originally
wanted to handle this situation by only passing expected arguments to
`find_versions` methods but there was a technical issue standing in
the way. I recently found an answer to the issue, so this also
replaces the existing `ExtractPlist` special case with generic logic
that checks the parameters for a strategy's `find_versions` method
and only passes expected arguments.
Replacing the aforementioned `find_versions` parameters with `Options`
ensures that the remaining parameters are fairly consistent across
strategies and any differences are handled by the aforementioned
logic. Outside of `ExtractPlist`, the only other difference is that
some `find_versions` methods have a `provided_content` parameter but
that's currently only used by tests (though it's intended for caching
support in the future). I will be renaming that parameter to `content`
in an upcoming PR and expanding it to the other strategies, which
should make them all consistent outside of `ExtractPlist`.
2025-02-11 18:04:38 -05:00
|
|
|
def self.find_versions(url:, regex: nil, options: Options.new, &block)
|
2021-07-28 13:20:12 -04:00
|
|
|
generated = generate_input_values(url)
|
2020-08-08 07:16:06 +05:30
|
|
|
|
2023-04-03 17:34:39 -07:00
|
|
|
version_data = PageMatch.find_versions(
|
livecheck: Add Options class
This adds a `Livecheck::Options` class, which is intended to house
various configuration options that are set in `livecheck` blocks,
conditionally set by livecheck at runtime, etc. The general idea is
that when we add features involving configurations options (e.g., for
livecheck, strategies, curl, etc.), we can make changes to `Options`
without needing to modify parameters for strategy `find_versions`
methods, `Strategy` methods like `page_headers` and `page_content`,
etc. This is something that I've been trying to improve over the years
and `Options` should help to reduce maintenance overhead in this area
while also strengthening type signatures.
`Options` replaces the existing `homebrew_curl` option (which related
strategies pass to `Strategy` methods and on to `curl_args`) and the
new `url_options` (which contains `post_form` or `post_json` values
that are used to make `POST` requests). I recently added `url_options`
as a temporary way of enabling `POST` support without `Options` but
this restores the original `Options`-based implementation.
Along the way, I added a `homebrew_curl` parameter to the `url` DSL
method, allowing us to set an explicit value in `livecheck` blocks.
This is something that we've needed in some cases but I also intend
to replace implicit/inferred `homebrew_curl` usage with explicit
values in `livecheck` blocks once this is available for use. My
intention is to eventually remove the implicit behavior and only rely
on explicit values. That will align with how `homebrew_curl` options
work for other URLs and makes the behavior clear just from looking at
the `livecheck` block.
Lastly, this removes the `unused` rest parameter from `find_versions`
methods. I originally added `unused` as a way of handling parameters
that some `find_versions` methods have but others don't (e.g., `cask`
in `ExtractPlist`), as this allowed us to pass various arguments to
`find_versions` methods without worrying about whether a particular
parameter is available. This isn't an ideal solution and I originally
wanted to handle this situation by only passing expected arguments to
`find_versions` methods but there was a technical issue standing in
the way. I recently found an answer to the issue, so this also
replaces the existing `ExtractPlist` special case with generic logic
that checks the parameters for a strategy's `find_versions` method
and only passes expected arguments.
Replacing the aforementioned `find_versions` parameters with `Options`
ensures that the remaining parameters are fairly consistent across
strategies and any differences are handled by the aforementioned
logic. Outside of `ExtractPlist`, the only other difference is that
some `find_versions` methods have a `provided_content` parameter but
that's currently only used by tests (though it's intended for caching
support in the future). I will be renaming that parameter to `content`
in an upcoming PR and expanding it to the other strategies, which
should make them all consistent outside of `ExtractPlist`.
2025-02-11 18:04:38 -05:00
|
|
|
url: generated[:url],
|
|
|
|
regex: regex || generated[:regex],
|
|
|
|
options:,
|
2021-07-28 13:20:12 -04:00
|
|
|
&block
|
|
|
|
)
|
2020-08-08 07:16:06 +05:30
|
|
|
|
2021-05-30 21:53:17 +05:30
|
|
|
if regex.blank?
|
2021-05-31 16:07:56 +05:30
|
|
|
# Filter out unstable versions using the old version scheme where
|
|
|
|
# the major version is below 40.
|
|
|
|
version_data[:matches].reject! do |_, version|
|
2022-06-10 19:07:05 -04:00
|
|
|
next if version.major >= 40
|
|
|
|
next if version.minor.blank?
|
|
|
|
|
|
|
|
(version.minor.to_i.odd? || version.minor >= 90) ||
|
|
|
|
(version.patch.present? && version.patch >= 90)
|
2021-05-30 21:53:17 +05:30
|
|
|
end
|
|
|
|
end
|
2021-07-28 13:20:12 -04:00
|
|
|
|
|
|
|
version_data
|
2020-08-08 07:16:06 +05:30
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|