From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: libircclient-1.10
Date: Thu, 09 May 2019 18:29:58 +0200 [thread overview]
Message-ID: <20190509162958.pzDTtpjgmyAG0SVpPGD8GM2PZoJvHH8V_orw60oi_SE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11495@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
New comment by maciozo on void-packages repository
https://github.com/void-linux/void-packages/pull/11495#issuecomment-490974924
Comment:
@pullmoll
> I tend to think if you just remove `do_install()` and let xbps-src do its job in the default `gnu-configure` build style it should work. All the things you did seem way too complicated.
Removing `do_install()` fails with:
```
=> libircclient-devel-1.10_1: running pkg_install ...
mv: cannot stat '/destdir//libircclient-1.10/usr/share/doc/libircclient/*': No such file or directory
=> ERROR: libircclient-devel-1.10_1: pkg_install: 'mv ${_destdir}/$files ${_pkgdestdir}/${_targetdir}' exited with 1
=> ERROR: in _vmove() at common/environment/setup/install.sh:232
=> ERROR: in _noglob_helper() at common/environment/setup/install.sh:12
=> ERROR: in pkg_install() at srcpkgs/libircclient-devel/template:28
```
With `template:28` being `vmove usr/share/doc/${sourcepkg}/*` in `libircclient-devel_package().pkg_install()`
Also removing `pkg_install()` fails with:
```
=> libircclient-devel-1.10_1: running pre-pkg hook: 99-pkglint ...
=> ERROR: libircclient-devel-1.10_1: PKGDESTDIR is empty and build_style != meta
=> ERROR: libircclient-devel-1.10_1: cannot continue with installation!
```
next prev parent reply other threads:[~2019-05-09 16:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 21:41 [PR PATCH] " voidlinux-github
2019-05-04 22:07 ` voidlinux-github
2019-05-04 23:28 ` [PR PATCH] [Updated] " voidlinux-github
2019-05-04 23:28 ` voidlinux-github
2019-05-04 23:35 ` voidlinux-github
2019-05-04 23:35 ` voidlinux-github
2019-05-04 23:37 ` voidlinux-github
2019-05-04 23:37 ` voidlinux-github
2019-05-05 0:03 ` voidlinux-github
2019-05-05 0:43 ` voidlinux-github
2019-05-07 17:39 ` voidlinux-github
2019-05-09 16:05 ` [PR PATCH] [Updated] " voidlinux-github
2019-05-09 16:05 ` voidlinux-github
2019-05-09 16:06 ` voidlinux-github
2019-05-09 16:10 ` voidlinux-github
2019-05-09 16:29 ` voidlinux-github [this message]
2019-05-09 16:48 ` [PR PATCH] [Updated] " voidlinux-github
2019-05-09 16:48 ` voidlinux-github
2019-05-09 17:17 ` voidlinux-github
2019-05-09 17:17 ` voidlinux-github
2019-05-09 17:21 ` voidlinux-github
2019-05-09 17:24 ` voidlinux-github
2019-05-09 18:01 ` voidlinux-github
2019-05-09 18:46 ` voidlinux-github
2019-05-09 18:48 ` voidlinux-github
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=20190509162958.pzDTtpjgmyAG0SVpPGD8GM2PZoJvHH8V_orw60oi_SE@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).