Skip to content
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

Divide the RPM task into two smaller tasks to make SetupBuilder more flexible #40

Open
JasonAtTR opened this issue Mar 23, 2017 · 2 comments

Comments

@JasonAtTR
Copy link

Hi @gamma ,
me again.
I have a question.
Could the rpm task be divided into two smaller tasks?
The SPEC file generate task and the rpm generate task?
So that if I have some special requirement for the rpm that the SetupBuilder does not support, I can call the SPEC file generate task first, then do some replacement in the SPEC file, at last call the rpm generate task.

@gamma
Copy link
Member

gamma commented Aug 3, 2017

are there any specific thing that you would like to be able to change or customize?

@mithomas
Copy link

mithomas commented Jun 11, 2018

I actually came across the same topic for the MSI task, where I would liked to have manipulated the generated WXS file (effectively to patch-in the install-directory in one of our internal plugins) - which is not possible since msi is one large task, not generateWxs->candle->light.

However, since I do think that more people might have this particular need, I opted to propose an extension of this plug-in instead where more people could benefit from it (hence #58).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants