Make it easier to supply custom archive to `packit srpm`
See original GitHub issueI see. Makes sense. But it would be good to have a little bit more easier / straightforward way how to prepare the upstream archive. For
fmf
I had to add three Makefile targets plus this:current_version_command: ["make", "packit-version"] actions: create-archive: - make packit-tarball - make packit-path
I believe it should be much simpler/shorter/obvious.
_Originally posted by @psss in https://github.com/packit-service/packit-service/issues/103#issuecomment-541553803_
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (9 by maintainers)
Top Results From Across the Web
Configuration - Packit
Under the hood this will use rsync --archive to synchronise the paths between the upstream and the dist-git repo. The fields for a...
Read more >How to create a Linux RPM package | Enable Sysadmin
This article shows you how to package a script into an RPM file for easy installation, updating, and removal from your Linux systems....
Read more >Modern development workflow for Fedora GNU/Linux ...
Source RPM (SRPM): *.src.rpm archive containing the sources and instructions (spec file) to build a binary package. The package definition in the RPM...
Read more >Globus Toolkit JIRA Archive - cs.wisc.edu
To reproduce, provide guc with a singe line input file, use the sync option, and dump-only option. (non-recursive) Specify a source and dest...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nice, thanks! Trying with https://github.com/psss/tmt/pull/249. Does not work…
@psss Your example looks good to me.
Yes, if it contains archive-name in the output.
We run the commands one-by-one and then go through the output in reverse order and for each line of the output (also in the reverse order), we check if it is an existing file. If yes, we accept that as a newly created archive. I know, it’s a bit complicated but should work for most situations.