Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

woof 20220202 #94258

Closed
wants to merge 1 commit into from
Closed

woof 20220202 #94258

wants to merge 1 commit into from

Conversation

samford
Copy link
Member

@samford samford commented Feb 1, 2022

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

This updates woof to the latest commit from 2021-06-09. The last release on the first-party site is from 2012-05-31 and the homepage directs users to the GitHub repository from 2020-06-24 onward.

Unfortunately, the repository has no tags/releases, so this PR is uses a commit archive as stable. With this situation, we'll simply have to manually check for new commits periodically and update the formula until/unless upstream starts tagging versions.

I've added depends_on "python@3.10", as the woof file is a Python script with a #!/usr/bin/env python3 hashbang. If this isn't necessary in this context, let me know and I'll remove it.

Past that, this adds license "GPL-2.0-or-later", referencing the license comment in the woof file, which reads:

#  woof -- an ad-hoc single file webserver
#  Copyright (C) 2004-2009 Simon Budig  <simon@budig.de>
#
#  This program is free software; you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.
#
#  This program is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  A copy of the GNU General Public License is available at
#  http://www.fsf.org/licenses/gpl.txt, you can also write to the
#  Free Software  Foundation, Inc., 59 Temple Place - Suite 330,
#  Boston, MA 02111-1307, USA.

@samford samford added the license License PRs label Feb 1, 2022
@BrewTestBot BrewTestBot added the python Python use is a significant feature of the PR or issue label Feb 1, 2022
@SMillerDev
Copy link
Member

Unfortunately, the repository has no tags/releases, so this PR is uses a commit archive as stable. With this situation, we'll simply have to manually check for new commits periodically and update the formula until/unless upstream starts tagging versions.

If there are releases we shouldn't make ones up. Either they start tagging or we remove the formula, with 8 installs in 30 days we're not exactly talking about a big formula here.

Copy link
Member

@SMillerDev SMillerDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See earlier comment

@samford
Copy link
Member Author

samford commented Feb 1, 2022

The last official release (from the homepage) is 20120531 but it doesn't support Python 3. Support was added in a 2012-05-31 commit but these changes aren't included as part of the release on the same date (it uses the commit before the Python 3 changes). The related commit wasn't made public until the GitHub project was created (2020-06-24).

The latest commit is from 2021-06-09, so the project doesn't seem to be dead. I'll create an issue to see if they'll start tagging versions (e.g., 2021-06-09). Edit: simon-budig/woof#15

@samford samford added the CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. label Feb 3, 2022
@samford samford changed the title woof 20210609 woof 20220202 Feb 3, 2022
@samford
Copy link
Member Author

samford commented Feb 3, 2022

By request, upstream tagged a version (woof-20220202), so I've updated this to use the tag archive.

With that out of the way, we just need to figure out if/how we can update the test to work on Linux.

@samford
Copy link
Member Author

samford commented Feb 3, 2022

By request, upstream tagged a version (woof-20220202), so I've updated this to use the tag archive.

The test failures on macOS 11 and Linux appeared to be related to system python3. That is to say, depends_on "python@3.10" doesn't do anything meaningful by itself when we're installing a Python script that uses a #!/usr/bin/env python3 shebang.

Calling inreplace "woof", "/usr/bin/env python3", Formula["python@3.10"].opt_bin/"python3" before bin.install "woof" works but is this the preferred approach for handling installed Python scripts like this?

@samford samford dismissed SMillerDev’s stale review February 4, 2022 03:19

Formula is now using a tagged version.

Formula/woof.rb Outdated Show resolved Hide resolved
@samford samford force-pushed the woof-20210609 branch 2 times, most recently from 7ef1144 to 6323a9d Compare February 5, 2022 23:19
@samford
Copy link
Member Author

samford commented Feb 5, 2022

This has been updated to use rewrite_shebang detected_python_shebang, "woof", which should resolve any outstanding requests/questions. I imagine this should be good to merge if/when this passes CI.

Co-authored-by: Branch Vincent <19800529+branchvincent@users.noreply.github.com>
@BrewTestBot
Copy link
Member

🤖 A scheduled task has triggered a merge.

@samford samford deleted the woof-20210609 branch February 7, 2022 14:10
@github-actions github-actions bot added the outdated PR was locked due to age label Mar 10, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. license License PRs outdated PR was locked due to age python Python use is a significant feature of the PR or issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants