1 |
On Sat, Feb 26, 2022 at 01:45:24PM -0500, Ionen Wolkens wrote: |
2 |
> On Sat, Feb 26, 2022 at 11:55:10AM -0600, William Hubbs wrote: |
3 |
> > If I change the instructions as you suggest to re-package upstream's |
4 |
> > tarball the name wouldn't need the -vendor suffix since the tarball would be a |
5 |
> > fork, but I'm not asking people to fork and repackage upstream's tarballs, just |
6 |
> > the vendor folder. Fortunately, there is no reason to fork since it is very |
7 |
> > easy to package the vendor folder with Go's tools. |
8 |
> |
9 |
> Doing: |
10 |
> tar ... project-1.0-vendor.tar.xz project-1.0/vendor |
11 |
> |
12 |
> would only package the "vendor" directory and not the whole |
13 |
> project directory. Then when auto-unpacked by src_unpack, the |
14 |
> vendor directory is added under project-1.0/ |
15 |
> |
16 |
> So this isn't repacking upstream's or a fork. |
17 |
|
18 |
Ok, I get what you are saying, but normally the directory you have the |
19 |
package in doesn't have a version number if you are working from a git |
20 |
repository, so I don't know how to get around this: |
21 |
|
22 |
cd path/to/project |
23 |
# note, no version number in "project" |
24 |
go mod vendor |
25 |
cd .. |
26 |
tar -acf project/vendor project-1.0-vendor.tar.xz |
27 |
|
28 |
This will put everything in the tarball under "project/" instead of |
29 |
"project-1.0/". |
30 |
|
31 |
Does tar have an option to change that top level path that I don't know |
32 |
about? |
33 |
|
34 |
Thanks, |
35 |
|
36 |
William |