Community
Participate
Working Groups
It would be nice if developers could export an SRPM and/or RPM to a defined location (not just the current workspace), similar to how the other export wizards operate.
Targeting for 3.0.
We will need to be careful on this one. We will still need to copy the source RPM back to the project as that is what is used as the base for the next export to generate a patch. What happens during an export is that if a change in the source code is detected, the RPM plugin takes the previous source RPM and explodes it in the work area and then copies the project to a parallel tree in the work area and runs the "diff" command to generate the patch. It is probably better keeping a copy of the source RPM in the project to do this. If we relied on the user maintaining a source RPM outside of the Eclipse workspace, we might have major problems later when they try to export the project again. There may be a better way of doing this, but I couldn't think of one.
Right. I don't think we should change the way we use the SRPM to generate diffs and track changes to the project over time; I can't think of a better way to do this either. With a binary RPM, we can just export straight to user-defined location. With an SRPM, we could just copy it to both the workspace and the user-defined export location.
I agree with the last statement, copy the source RPM to both locations and the binary RPM just to the user-specified location.
As discussed in the weekly meeting -- all enhancements requests that had a target milestone of 3.0 but were assigned to an inbox owner (which is an invalid combination), have been moved to Target Milestone "--".
