-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ghost entries #56
Labels
Comments
Yea, I think there is a bug :) I think using I guess a solution would be to (in the case of ghost) ignore the fact that the file/directory doesn't exists. |
dranuhl
added a commit
to dranuhl/rpm-builder
that referenced
this issue
Nov 22, 2021
dranuhl
added a commit
to dranuhl/rpm-builder
that referenced
this issue
Nov 29, 2021
dranuhl
added a commit
to dranuhl/rpm-builder
that referenced
this issue
Nov 29, 2021
This was referenced Nov 29, 2021
Merged
ctron
pushed a commit
that referenced
this issue
Nov 29, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to specify a ghost entry, but the plugin requires a file, directory or collect element to be specified for it anyway, which does not seem to make much sense to me.
For example:
Yields:
[ERROR] Failed to execute goal de.dentrassi.maven:rpm:1.6.0:rpm (default) on project myapp: Exactly one of 'file', 'directory', 'linkTo' or 'collect' must be specified.
If adding a file element referring to a non-existing file to the above entry, will lead to the following trace:
Using collect element that does not find a file, will not lead to an error, but the produced RPM will not know about the ghost file either.
Using skip will not lead to an error in either case, but the produced RPM will not know about the ghost file either.
So it seems that currently the only way to refer to an existing empty file, which seems to be cumbersome and not intuitive.
The text was updated successfully, but these errors were encountered: