Github messages for voidlinux
 help / color / mirror / Atom feed
From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: flyctl-0.0.351
Date: Sat, 06 Aug 2022 23:01:45 +0200	[thread overview]
Message-ID: <20220806210145.0dApHaRwSTfz6lKEaDh9OA2LCRBOKdSP4ePBx8RwmIA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37950@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

There's a closed pull request on the void-packages repository

New package: flyctl-0.0.351
https://github.com/void-linux/void-packages/pull/37950

Description:
`flyctl` is a command-line interface for fly.io.

fly.io is [somewhat](https://xeiaso.net/blog/fly.io-heroku-replacement) like Heroku.

#### Testing the changes
- I tested the changes in this PR **briefly**.

```
❯ ./xbps-src pkg flyctl
<...>
❯ xi -y flyctl
<...>
❯ which flyctl
/usr/bin/flyctl
❯ flyctl version
flyctl v0.0.0-1657391288+dev linux/amd64 Commit: <commit> BuildDate: 2022-07-09T18:28:08Z
```

That `<commit>` seems to be a problem even if I build inside a git repo:
```
❯ gh repo clone superfly/flyctl
<...>
❯ cd flyctl
❯ make
<...>
❯ bin/flyctl version
flyctl v0.0.0-1657392531+dev linux/amd64 Commit: <commit> BuildDate: 2022-07-09T18:48:51Z
```

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements).


      parent reply	other threads:[~2022-08-06 21:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 18:52 [PR PATCH] " Goorzhel
2022-07-09 18:53 ` classabbyamp
2022-07-09 18:57 ` [PR REVIEW] " classabbyamp
2022-07-09 19:21 ` [PR PATCH] [Updated] " Goorzhel
2022-07-09 19:51 ` Goorzhel
2022-07-09 20:01 ` Goorzhel
2022-07-09 20:02 ` Goorzhel
2022-07-09 20:02 ` Goorzhel
2022-07-09 20:08 ` Goorzhel
2022-07-10  0:24 ` [PR REVIEW] " CameronNemo
2022-07-10  0:41 ` classabbyamp
2022-07-10  1:46 ` [PR PATCH] [Updated] " Goorzhel
2022-07-10  1:46 ` Goorzhel
2022-07-10  1:57 ` classabbyamp
2022-07-12  7:12 ` [PR PATCH] [Updated] " Goorzhel
2022-07-12  7:12 ` Goorzhel
2022-07-12  7:13 ` Goorzhel
2022-07-21  6:30 ` Goorzhel
2022-07-21 13:32 ` classabbyamp
2022-07-24 19:39 ` [PR PATCH] [Updated] " Goorzhel
2022-07-24 19:39 ` Goorzhel
2022-07-24 19:40 ` Goorzhel
2022-07-24 19:40 ` [PR PATCH] [Updated] " Goorzhel
2022-08-06 21:01 ` Goorzhel
2022-08-06 21:01 ` Goorzhel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220806210145.0dApHaRwSTfz6lKEaDh9OA2LCRBOKdSP4ePBx8RwmIA@z \
    --to=goorzhel@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).