Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346134 - Move RPM related API from Eclipse Fedora Packager to RPM Spec File Editor
Summary: Move RPM related API from Eclipse Fedora Packager to RPM Spec File Editor
Status: CLOSED WONTFIX
Alias: None
Product: Linux Tools
Classification: Tools
Component: RPM (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Alexander Kurtakov CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-17 14:33 EDT by Severin Gehwolf CLA
Modified: 2014-11-13 06:54 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Severin Gehwolf CLA 2011-05-17 14:33:32 EDT 
Eclipse Fedora Packager[1] (rpm plug-in) is doing some RPM related things. It would be a good idea to move some/all of it to the RPM Spec File editor plug-in.

[1] https://fedorahosted.org/eclipse-fedorapackager/
Comment 1 Andrew Overholt CLA 2011-05-17 16:02:57 EDT 
What types of things do you have in mind, Severin?
Comment 2 Severin Gehwolf CLA 2011-05-17 16:25:08 EDT 
(In reply to comment #1)
> What types of things do you have in mind, Severin?

Alex and I were talking briefly about this. Something JGit like. Provide API for RPM builds. Essentially, something very similar to RpmBuildCommand in Eclipse Fedora Packager.

It shouldn't be too hard to move things there. Just rip off some EFP specific deps and it should be good to go.
Comment 3 Eclipse Genie CLA 2014-06-07 15:59:33 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Alexander Kurtakov CLA 2014-11-13 06:54:37 EST 
Closing the bug. There is no point in poluting the queue if nothing happens.