From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [Need Help] New package: materia-gtk-theme-20190831
Date: Mon, 09 Sep 2019 09:13:42 +0200 [thread overview]
Message-ID: <20190909071342.xmtVOtLCXpVH3Nigs1Rgo2EGnR9w1C75QkgCgsZFK2U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14247@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
New comment by lugubris on void-packages repository
https://github.com/void-linux/void-packages/pull/14247#issuecomment-529330600
Comment:
Danh Doan @ 2019-09-08 01:42 UTC:
> Here is a working template:
> ```sh
> # Template file for 'materia-gtk-theme'
> pkgname=materia-gtk-theme
> version=20190831
> revision=1
> archs=noarch
> wrksrc="materia-theme-${version}"
> depends="gtk+3 gnome-themes-extra"
> short_desc="Material Design theme for GNOME/GTK based desktop environments"
> maintainer="Lugubris <lugubris@disroot.org>"
> license="GPL-2.0-only"
> homepage=https://github.com/nana-4/materia-theme
> distfiles="https://github.com/nana-4/materia-theme/archive/v${version}.tar.gz"
> checksum=7ab5423ecaef50d5e9cf94038f9a35a1bcb87e7b218edff316b4f92d4b7b8b67
>
> do_install() {
> vmkdir usr/share/themes
> ./install.sh -d "${DESTDIR}/usr/share/themes"
> }
> ```
That didn't work, I had some problems with the tar command, current
template works.
relevant: https://www.xkcd.com/1168/
foo.tar has a directory bar so the structure is:
foo.tar
-bar
--file1
--subdir1
--file2
..
When I extract foo.tar it creates a directory bar, like this:
wrksrc
-foo.tar
-bar
--file1
..
I want it to extract all contents of bar to wrksrc, like:
wrksrc
-foo.tar
-file1
-subdir1
-file2
..
Currently I cd into bar and then run ./install which works so I guess
its fine.
--
Lugubris
next prev parent reply other threads:[~2019-09-09 7:13 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 11:54 [PR PATCH] " voidlinux-github
2019-09-06 11:56 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-06 11:56 ` voidlinux-github
2019-09-06 13:01 ` voidlinux-github
2019-09-06 13:01 ` voidlinux-github
2019-09-06 13:03 ` voidlinux-github
2019-09-06 13:03 ` voidlinux-github
2019-09-06 13:35 ` voidlinux-github
2019-09-06 13:35 ` voidlinux-github
2019-09-06 14:41 ` voidlinux-github
2019-09-06 14:43 ` voidlinux-github
2019-09-06 14:48 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-06 14:48 ` voidlinux-github
2019-09-06 14:51 ` voidlinux-github
2019-09-06 14:51 ` voidlinux-github
2019-09-06 14:54 ` voidlinux-github
2019-09-06 15:05 ` voidlinux-github
2019-09-07 6:03 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-07 6:03 ` voidlinux-github
2019-09-07 6:08 ` voidlinux-github
2019-09-07 6:08 ` voidlinux-github
2019-09-07 6:09 ` voidlinux-github
2019-09-07 6:09 ` voidlinux-github
2019-09-07 6:12 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-07 6:12 ` voidlinux-github
2019-09-07 6:35 ` voidlinux-github
2019-09-07 6:35 ` voidlinux-github
2019-09-07 6:42 ` voidlinux-github
2019-09-07 6:42 ` voidlinux-github
2019-09-07 6:48 ` voidlinux-github
2019-09-07 6:48 ` voidlinux-github
2019-09-07 7:06 ` voidlinux-github
2019-09-07 7:06 ` voidlinux-github
2019-09-07 7:11 ` voidlinux-github
2019-09-07 7:11 ` voidlinux-github
2019-09-07 7:18 ` voidlinux-github
2019-09-07 7:18 ` voidlinux-github
2019-09-07 7:25 ` voidlinux-github
2019-09-08 1:42 ` [Need Help] " voidlinux-github
2019-09-08 6:42 ` voidlinux-github
2019-09-09 5:37 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-09 5:37 ` voidlinux-github
2019-09-09 5:48 ` voidlinux-github
2019-09-09 5:48 ` voidlinux-github
2019-09-09 5:55 ` voidlinux-github
2019-09-09 5:55 ` voidlinux-github
2019-09-09 6:02 ` voidlinux-github
2019-09-09 6:02 ` voidlinux-github
2019-09-09 6:12 ` voidlinux-github
2019-09-09 6:12 ` voidlinux-github
2019-09-09 6:21 ` voidlinux-github
2019-09-09 6:21 ` voidlinux-github
2019-09-09 6:30 ` voidlinux-github
2019-09-09 6:30 ` voidlinux-github
2019-09-09 6:45 ` voidlinux-github
2019-09-09 6:45 ` voidlinux-github
2019-09-09 7:01 ` voidlinux-github
2019-09-09 7:01 ` voidlinux-github
2019-09-09 7:08 ` voidlinux-github
2019-09-09 7:08 ` voidlinux-github
2019-09-09 7:12 ` voidlinux-github
2019-09-09 7:13 ` voidlinux-github [this message]
2019-09-09 7:15 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-09 7:15 ` voidlinux-github
2019-09-09 7:23 ` voidlinux-github
2019-09-09 7:57 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-09 7:57 ` voidlinux-github
2019-09-09 7:58 ` voidlinux-github
2019-09-09 8:00 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-09 8:00 ` voidlinux-github
2019-09-11 17:29 ` voidlinux-github
2019-09-11 17:41 ` voidlinux-github
2019-09-13 5:00 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-13 5:00 ` voidlinux-github
2020-03-29 18:40 ` hfel
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=20190909071342.xmtVOtLCXpVH3Nigs1Rgo2EGnR9w1C75QkgCgsZFK2U@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).