From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 02/02: gnu: syncthing: Prepare for cross-compiling.
Date: Sun, 15 Aug 2021 16:42:19 -0400 [thread overview]
Message-ID: <YRl8K/YA/7js03lV@jasmine.lan> (raw)
In-Reply-To: <20210426183356.3D8B820DD2@vcs0.savannah.gnu.org>
On Mon, Apr 26, 2021 at 02:33:56PM -0400, guix-commits@gnu.org wrote:
> efraim pushed a commit to branch master
> in repository guix.
>
> commit b33f5d7ff0627424a06fd0416761cd81c350e20a
> Author: Efraim Flashner <efraim@flashner.co.il>
> AuthorDate: Mon Apr 26 21:30:15 2021 +0300
>
> gnu: syncthing: Prepare for cross-compiling.
>
> * gnu/packages/syncthing.scm (syncthing)[arguments]: Add custom
> 'pre-build phase to not set a local GOBIN directory. Adjust custom
> 'build and 'install phases accordingly.
This commit broke splitting the package into two outputs "out" and
"utils".
When everything is working, the utils output should look like this:
------
$ tree /gnu/store/zansw6f7i61glpa2f5hsbpazwg6qfi2v-syncthing-1.15.1-utils
/gnu/store/zansw6f7i61glpa2f5hsbpazwg6qfi2v-syncthing-1.15.1-utils
├── bin
│ ├── stcompdirs
│ ├── stcrashreceiver
│ ├── stdisco
│ ├── stdiscosrv
│ ├── stevents
│ ├── stfileinfo
│ ├── stfinddevice
│ ├── stfindignored
│ ├── stgenfiles
│ ├── stindex
│ ├── strelaypoolsrv
│ ├── strelaysrv
│ ├── stsigtool
│ ├── stvanity
│ ├── stwatchfile
│ ├── uraggregate
│ └── ursrv
└── share
├── doc
│ └── syncthing-1.15.1
│ └── LICENSE
└── man
├── man1
│ ├── stdiscosrv.1.gz
│ └── strelaysrv.1.gz
├── man5
│ ├── syncthing-config.5.gz
│ └── syncthing-stignore.5.gz
└── man7
├── syncthing-bep.7.gz
├── syncthing-device-ids.7.gz
├── syncthing-event-api.7.gz
├── syncthing-faq.7.gz
├── syncthing-globaldisco.7.gz
├── syncthing-localdisco.7.gz
├── syncthing-networking.7.gz
├── syncthing-relay.7.gz
├── syncthing-rest-api.7.gz
├── syncthing-security.7.gz
└── syncthing-versioning.7.gz
8 directories, 33 files
------
The broken state looks like this:
------
$ tree /gnu/store/b1jz5rnwjgzvl7hd99rd1r5958rwxh5x-syncthing-1.15.1-utils
/gnu/store/b1jz5rnwjgzvl7hd99rd1r5958rwxh5x-syncthing-1.15.1-utils
└── share
├── doc
│ └── syncthing-1.15.1
│ └── LICENSE
└── man
├── man1
│ ├── stdiscosrv.1.gz
│ └── strelaysrv.1.gz
├── man5
│ ├── syncthing-config.5.gz
│ └── syncthing-stignore.5.gz
└── man7
├── syncthing-bep.7.gz
├── syncthing-device-ids.7.gz
├── syncthing-event-api.7.gz
├── syncthing-faq.7.gz
├── syncthing-globaldisco.7.gz
├── syncthing-localdisco.7.gz
├── syncthing-networking.7.gz
├── syncthing-relay.7.gz
├── syncthing-rest-api.7.gz
├── syncthing-security.7.gz
└── syncthing-versioning.7.gz
7 directories, 16 files
------
next parent reply other threads:[~2021-08-15 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210426183354.7136.54877@vcs0.savannah.gnu.org>
[not found] ` <20210426183356.3D8B820DD2@vcs0.savannah.gnu.org>
2021-08-15 20:42 ` Leo Famulari [this message]
2021-08-15 20:49 ` 02/02: gnu: syncthing: Prepare for cross-compiling Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YRl8K/YA/7js03lV@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).