<feed xmlns='http://www.w3.org/2005/Atom'>
<title>brew/Library/Homebrew/extend/os/mac/utils, branch 1.2.0</title>
<subtitle>🍺 The missing package manager for macOS</subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/brew/'/>
<entry>
<title>bottles: --force-bottle feigns or_later.</title>
<updated>2017-01-02T16:05:14+00:00</updated>
<author>
<name>Mike McQuaid</name>
</author>
<published>2017-01-02T16:05:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/brew/commit/?id=79f9896d2ffd03819236318c9f0742d40f1826ac'/>
<id>79f9896d2ffd03819236318c9f0742d40f1826ac</id>
<content type='text'>
When reproducing issues with software that hasn’t been bottled yet on
your version of macOS it can sometimes be helpful to use `or_later`
bottle functionality i.e. just use the bottle for the latest version of
macOS available. This maps well to the existing `--force-bottle`
argument so it will now act as if the latest bottle has a `or_later`
ending.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When reproducing issues with software that hasn’t been bottled yet on
your version of macOS it can sometimes be helpful to use `or_later`
bottle functionality i.e. just use the bottle for the latest version of
macOS available. This maps well to the existing `--force-bottle`
argument so it will now act as if the latest bottle has a `or_later`
ending.
</pre>
</div>
</content>
</entry>
<entry>
<title>software_spec: no `_or_later` in bottle filenames.</title>
<updated>2016-11-05T20:13:42+00:00</updated>
<author>
<name>Mike McQuaid</name>
</author>
<published>2016-11-05T20:13:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/brew/commit/?id=1f6c26a2e4b97ad90e6b8623df90daf4e07086a9'/>
<id>1f6c26a2e4b97ad90e6b8623df90daf4e07086a9</id>
<content type='text'>
It's more useful to be able to "bless" an existing bottle to be used on
later OSs (e.g. where it cannot yet be built) than it is to have to
create a new, identical bottle just to have a different filename.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It's more useful to be able to "bless" an existing bottle to be used on
later OSs (e.g. where it cannot yet be built) than it is to have to
create a new, identical bottle just to have a different filename.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix Style/GuardClause.</title>
<updated>2016-09-24T10:24:35+00:00</updated>
<author>
<name>Markus Reiter</name>
</author>
<published>2016-09-23T20:02:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/brew/commit/?id=58e36c73193befb57d351344cea2a4a33fef850d'/>
<id>58e36c73193befb57d351344cea2a4a33fef850d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Style/Alias: Prefer `alias`.</title>
<updated>2016-09-23T16:19:53+00:00</updated>
<author>
<name>Markus Reiter</name>
</author>
<published>2016-09-23T16:13:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/brew/commit/?id=e851c9bf6c3adda268f1a307d6b49acb1ad1852d'/>
<id>e851c9bf6c3adda268f1a307d6b49acb1ad1852d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Make bottle code cross-platform.</title>
<updated>2016-05-08T15:51:22+00:00</updated>
<author>
<name>Mike McQuaid</name>
</author>
<published>2016-04-25T16:57:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/brew/commit/?id=931e292bf12b8e05f6586ac7721255b35f04a389'/>
<id>931e292bf12b8e05f6586ac7721255b35f04a389</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
