Not really, because the unwanted binaries are only half the story. Unwanted
junk ends up in the source directories too, despite best attempts to do not
litter :smile: I want to know precisely what ends up in the tarball, and "cp -a
here there" doesn't cut it.
I'm not looking for help here,
@pmatilai does using a build directory that is outside of the source directory
(something like `~/repos-build/rpm`) help? IIRC this is best practice for at
least some build systems.
--
Reply to this email directly or view it on GitHub:
Of course, what we really should aim to is eliminating the human factor from
release creation as much as possible. Once you have a script which grabs a
clean git checkout, runs doc pre-generation automatically and then produces the
dist tarball from that known state that's not accessible to us
Oh, yep:
> [pmatilai︎localhost _build]$ make package_source
Run CPack packaging tool for source...
CPack: Create package using TBZ2
CPack: Install projects
CPack: - Install directory: /home/pmatilai/repos/rpm
CPack Error: Problem copying file:
/home/pmatilai/repos/rpm/_build/tests/testing/usr/
My initial impression from cpack is that it merrily copies whatever random crap
may be in your tree, unless you have it excluded. It's entirely possible I'm
mistaken and/or that it's possible to it more selective, but until that time I
trust git for the task about a 100 times more :sweat_smile:
@Conan-Kudo That was my thought too.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/commit/61bb33e593c0fa56aaca935da2007fe9bb848fd2#commitcomment-87619137
You are receiving this because you are subscribed to this thread.
Message ID:
@pmatilai You can use CPack for this, I believe?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/commit/61bb33e593c0fa56aaca935da2007fe9bb848fd2#commitcomment-87617945
You are receiving this because you are subscribed to this thread.
Message
