From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] add vdevel helper
Date: Thu, 16 Mar 2023 07:13:10 +0100 [thread overview]
Message-ID: <20230316061310.BtjShbyjIFWJiy8QjBQQai-9p9P_YXEyAlLIGVZ4Dgk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39274@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
There's a closed pull request on the void-packages repository
[RFC] add vdevel helper
https://github.com/void-linux/void-packages/pull/39274
Description:
This adds a helper for the install phase, `vdevel`, which moves commonly-moved patterns/directories to the subpkg in which it's called using `vmove`.
Based on these Highly Scientific™ stats and the existing list in Manual.md, I came up with a list of patterns and directories to move.
<details><summary>The Numbers</summary>
```
count command
1859 vmove usr/include
1664 vmove usr/lib/*.so
1414 vmove usr/lib/pkgconfig
750 vmove usr/lib/*.a
331 vmove usr/lib/cmake
182 vmove usr/share/gir-1.0
154 vmove usr/share/man/man3
112 vmove usr/lib/qt5/mkspecs
101 vmove usr/share/gtk-doc
94 vmove usr/share/vala
64 vmove usr/share/aclocal
17 vmove usr/share/info
15 vmove usr/share/man
14 vmove usr/lib/*.la
12 vmove usr/share/cmake
10 vmove usr/share/pkgconfig
```
</details>
**(Should `usr/share/gtk-doc` and/or `usr/share/man/man3` be added to the `vdevel` list?)**
If a pattern or directory is not matched, only a warning is printed, describing what wasn't found.
This should be compatible with many `-devel` packages, but not all, and that is okay. Also, if additional files need to be moved, they can be `vmove`d manually.
Some examples of `vdevel` in action are included.
Prior art: #21721
#### Testing the changes
- I tested the changes in this PR: **YES**
prev parent reply other threads:[~2023-03-16 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 4:18 [PR PATCH] " classabbyamp
2022-09-14 4:23 ` [PR PATCH] [Updated] " classabbyamp
2022-09-22 8:17 ` thypon
2022-09-22 11:15 ` classabbyamp
2022-09-22 17:09 ` Vaelatern
2022-09-22 17:09 ` Vaelatern
2022-12-22 1:57 ` github-actions
2023-03-16 6:13 ` classabbyamp [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=20230316061310.BtjShbyjIFWJiy8QjBQQai-9p9P_YXEyAlLIGVZ4Dgk@z \
--to=classabbyamp@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).