Github messages for voidlinux
 help / color / mirror / Atom feed
From: nilium <nilium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: booster-0.6
Date: Tue, 09 Nov 2021 22:17:57 +0100	[thread overview]
Message-ID: <20211109211757.KY8iuVSaG4NNdxzScD75gBB1jT7Hm2FWsJcms4kEcg8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29434@inbox.vuxu.org>

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

New comment by nilium on void-packages repository

https://github.com/void-linux/void-packages/pull/29434#issuecomment-964556540

Comment:
> @nilium is it Go upstream style guide or Void one to have `go.mod` at the root of the project?

The short answer to this is that it's both. There is limited support for projects with further nested go.mod files as far as Go is concerned but there's never been a reason to support them in the build style. To the best of my knowledge, this is also the only instance I've seen of a project being organized this way, so I'm going to say that it does not fit the build style or expectations of Go in general, and that it would require special handling in the build script.

  parent reply	other threads:[~2021-11-09 21:17 UTC|newest]

Thread overview: 141+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-13 14:53 [PR PATCH] New package: booster-0.3 travankor
2021-03-13 15:16 ` [PR REVIEW] " ericonr
2021-03-13 22:55 ` travankor
2021-03-13 23:10 ` travankor
2021-03-13 23:11 ` travankor
2021-03-13 23:30 ` ericonr
2021-03-15  3:06 ` [PR PATCH] [Updated] " travankor
2021-03-15  3:17 ` travankor
2021-03-15  3:32 ` travankor
2021-03-15  3:35 ` travankor
2021-03-15  3:50 ` travankor
2021-03-15  3:55 ` travankor
2021-03-16 14:03 ` travankor
2021-04-11  4:01 ` [PR REVIEW] " ericonr
2021-04-11 17:31 ` [PR PATCH] [Updated] New package: booster-0.4 travankor
2021-04-12 13:21 ` travankor
2021-04-25  2:03 ` travankor
2021-04-25  3:38 ` travankor
2021-04-25  3:51 ` travankor
2021-04-25 13:16 ` travankor
2021-04-25 17:08 ` [PR REVIEW] " travankor
2021-04-25 17:14 ` [PR PATCH] [Updated] " travankor
2021-04-25 17:17 ` travankor
2021-04-25 17:19 ` [PR PATCH] [Updated] " travankor
2021-05-13 13:19 ` travankor
2021-05-15 13:36 ` [PR PATCH] [Updated] New package: booster-0.5 travankor
2021-05-18 14:13 ` UsernameRandomlyGenerated
2021-05-24 16:15 ` dkwo
2021-05-27 18:50 ` dkwo
2021-06-01 19:13 ` travankor
2021-06-06  8:39 ` dkwo
2021-06-12 17:23 ` dkwo
2021-06-12 17:24 ` dkwo
2021-06-12 17:26 ` dkwo
2021-06-12 17:52 ` paper42
2021-06-12 17:52 ` paper42
2021-06-12 18:15 ` dkwo
2021-06-23  3:08 ` anatol
2021-06-30  8:33 ` dkwo
2021-06-30  9:14 ` travankor
2021-06-30 13:06 ` [PR PATCH] [Updated] " travankor
2021-07-01  3:51 ` [PR REVIEW] " ericonr
2021-07-01  3:51 ` ericonr
2021-07-01  3:58 ` ericonr
2021-07-01  4:01 ` ericonr
2021-07-01 13:03 ` [PR PATCH] [Updated] " travankor
2021-07-01 13:05 ` travankor
2021-07-01 13:08 ` [PR PATCH] [Updated] " travankor
2021-07-01 15:15 ` anatol
2021-07-02  9:36 ` dkwo
2021-07-20 17:12 ` anatol
2021-07-21 15:48 ` [PR PATCH] [Updated] " travankor
2021-07-22  7:43 ` New package: booster-0.6 dkwo
2021-09-11 23:27 ` anatol
2021-09-12  6:31 ` dkwo
2021-09-12 10:36 ` [PR REVIEW] " paper42
2021-09-12 10:36 ` paper42
2021-09-12 10:36 ` paper42
2021-09-12 11:28 ` ahesford
2021-09-12 11:36 ` paper42
2021-09-13 14:42 ` [PR PATCH] [Updated] " travankor
2021-09-13 14:44 ` travankor
2021-09-14 14:02 ` travankor
2021-09-14 14:08 ` travankor
2021-09-14 14:16 ` travankor
2021-09-14 14:25 ` travankor
2021-09-14 22:57 ` travankor
2021-09-27 23:37 ` anatol
2021-10-12  8:48 ` dkwo
2021-10-14 19:32 ` anatol
2021-10-16 11:56 ` dkwo
2021-10-16 12:21 ` dkwo
2021-11-07  9:54 ` dkwo
2021-11-07 10:19 ` dkwo
2021-11-07 14:14 ` anatol
2021-11-07 14:15 ` anatol
2021-11-07 15:17 ` anatol
2021-11-08 10:01 ` dkwo
2021-11-08 14:04 ` anatol
2021-11-08 17:19 ` dkwo
2021-11-08 20:45 ` anatol
2021-11-09 13:13 ` dkwo
2021-11-09 19:05 ` nilium
2021-11-09 20:59 ` anatol
2021-11-09 21:17 ` nilium [this message]
2021-11-10  9:25 ` dkwo
2021-11-10 15:22 ` anatol
2021-11-10 21:38 ` [PR PATCH] [Updated] " travankor
2021-11-10 21:48 ` travankor
2021-11-10 23:12 ` [PR REVIEW] New package: booster-0.7 anatol
2021-11-11  7:59 ` travankor
2021-11-12  1:31 ` anatol
2021-11-12 10:12 ` dkwo
2021-11-12 16:03 ` anatol
2021-11-12 21:46 ` [PR PATCH] [Updated] " travankor
2021-11-12 21:47 ` [PR REVIEW] " travankor
2021-11-13  9:29 ` dkwo
2021-12-03  2:56 ` anatol
2022-03-06 21:13 ` anatol
2022-05-28  0:07 ` [PR PATCH] [Updated] " travankor
2022-07-03 11:46 ` dkwo
2022-07-03 13:05 ` anatol
2022-07-03 13:08 ` anatol
2022-07-03 13:10 ` anatol
2022-07-03 18:58 ` dkwo
2022-07-18  1:57 ` anatol
2022-07-23  9:09 ` oynqr
2022-07-31 23:01 ` CameronNemo
2022-07-31 23:45 ` CameronNemo
2022-08-01  3:56 ` anatol
2022-08-01  3:59 ` [PR REVIEW] " anatol
2022-08-01 13:40 ` [PR PATCH] [Updated] " travankor
2022-08-01 13:42 ` travankor
2022-08-01 13:46 ` [PR PATCH] [Updated] New package: booster-0.8 travankor
2022-08-01 14:55 ` [PR REVIEW] " CameronNemo
2022-08-01 14:55 ` CameronNemo
2022-08-01 19:57 ` [PR PATCH] [Updated] " travankor
2022-08-26 10:42 ` JamiKettunen
2022-09-08 20:08 ` [PR PATCH] [Updated] " travankor
2022-09-26 12:21 ` New package: booster-0.9 ahesford
2022-10-03 15:08 ` dkwo
2022-10-09 20:36 ` [PR PATCH] [Updated] " travankor
2022-10-09 23:11 ` [PR REVIEW] " CameronNemo
2022-10-09 23:31 ` ahesford
2022-10-09 23:33 ` ahesford
2022-10-10  2:51 ` CameronNemo
2022-10-10  6:58 ` [PR PATCH] [Updated] " travankor
2022-10-10 14:02 ` ahesford
2022-10-10 14:33 ` ahesford
2022-10-10 14:49 ` ahesford
2022-10-10 14:58 ` ahesford
2022-10-10 14:59 ` ahesford
2022-10-10 18:14 ` CameronNemo
2022-10-10 18:14 ` CameronNemo
2022-10-10 18:26 ` ahesford
2022-10-10 20:51 ` anatol
2022-10-10 20:51 ` anatol
2022-10-10 22:03 ` ahesford
2022-10-14 20:13 ` dkwo
2022-10-14 20:41 ` ahesford
2022-10-14 20:41 ` [PR PATCH] [Closed]: " ahesford

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=20211109211757.KY8iuVSaG4NNdxzScD75gBB1jT7Hm2FWsJcms4kEcg8@z \
    --to=nilium@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).