ALV-223: CI for building tarball packages #39
Conversation
Signed-off-by: Alf-Rune Siqveland <alf.rune@northern.tech>
The default prefix paths are set to the Makefile defaults. If DESTDIR is set, change the defaults to comply with Debian packaging. Signed-off-by: Alf-Rune Siqveland <alf.rune@northern.tech>
alfrunes
force-pushed
the
ALV-223
branch
5 times, most recently
from
bfad95a to
dd41123
Compare
alfrunes
changed the title
alfrunes
force-pushed
the
ALV-223
branch
2 times, most recently
from
87e347a to
a91a086
Compare
alfrunes
changed the title
|
I changed the PR to only create tarballs that can be installed by |
A tarball is as generic as it gets :) The only think to take care of is the configuration file. This is likely for a user to modify and then it would be unexpected that upgrading to a new tarball will replace the file. This we can take care in the install script somehow. I honestly think that it is the best for now given the requirements. We can always migrate to Debian or rpm packages later if we want something more streamlined. |
Signed-off-by: Alf-Rune Siqveland <alf.rune@northern.tech>
Signed-off-by: Alf-Rune Siqveland <alf.rune@northern.tech>
Makefile
Outdated
| dist: DESTDIR=dist/nt-connect_$(VERSION)_$(GOOS)_$(GOARCH) | ||
| dist: | ||
| @make DESTDIR=$(DESTDIR) -B install | ||
| tar -C $(DESTDIR) -czf $(DESTDIR).tar.gz . |
There was a problem hiding this comment.
FYI all files are uploaded to the pipeline Artifacts:
Consider removing $(DESTDIR)
There was a problem hiding this comment.
Ahh, right! I'll instead install into a temporary directory and only create the tarballs in dist.
There was a problem hiding this comment.
I just made it really simple by adding --remove-files to the tar command so it removes them as they are added to the archive.
Signed-off-by: Alf-Rune Siqveland <alf.rune@northern.tech>
Signed-off-by: Alf-Rune Siqveland <alf.rune@northern.tech>
3 participants
Fixed up the Makefile and added a simple script to build Debian package for
amd64,arm64andarmhf.