On 03/01/15 20:26, Hedayat Vatankhah wrote:
/*Luya Tshimbalanga*/ wrote on Fri, 02 Jan 2015 17:29:14 -0800:
Add-ons cannot cover development libraries, unless every library is an add-on for all IDEs!
Then is IDE packaging issue. When it comes of using a development applications, the software should suggest installing the missing library. If Gnome Video is able to prompt uses to install missing component, then why shouldn't be possible for IDE application to do the same? Granted I don't know well the functionality but the logic is application should detect and suggest adding the missing function.
Hmm... that's weird, I can't understand what you mean. Gnome Video's job is very easy: a video has a special format, and there are specific plugins to enable playing that. However, assume that I need an XML library for C++: 1. How can I tell the IDE that I need an XML library? 2. What should IDE do if there are 5 different XML libraries for C++? How should I tell it which one I want, specially if I don't know what should I use already, and want to see what is available out there? To me, it seems like implementing a special purpose software manager inside IDE with almost all functionality GNOME Software provides. As I said in another post, user reviews/rating for development libraries (like what GNOME Software provides for applications) can be really helpful when a developer wants to choose a library for a specific purpose.
In other words: there is a difference between the toolchain and project dependencies.
The toolchain e. g. eclipse + gcc etc. can be probably partly be fixed using IDE dependencies, DevAssistant and similar setups reflecting general tool-set dependencies, agreed.
OTOH, the dependencies for a specific project cannot really be handled this way. Such libraries are specific for the code you build, not the tools. Making them dependencies of e. g., eclipse just doesn't make any sense.
Cheers! --alec -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
