Talk:Installing third party softwares in terminal/Build/KDE4/on virtual machines: Difference between revisions
| Line 11: | Line 11: | ||
The download file will be rather large, however compression should be able to find patterns between intermediate objects and the final products, so hopefully a compressed copy will only be a kde install larger than kde+source | The download file will be rather large, however compression should be able to find patterns between intermediate objects and the final products, so hopefully a compressed copy will only be a kde install larger than kde+source | ||
-- [[User: | -- [[User:AaronPeterson]] | ||
Revision as of 17:22, 5 September 2010
It is not clear who "I" is. Please avoid using the I-form as this does not provide any useful information for readers, especially when several people changed the page. --Dhaumann
Proposal for this page
This would be a super duper helpfull way to get people into developing this software.
We should provide virtual machine images of a basic suse or debian enviornment, with eclipse or at least kdevelop set up, with all the kde svn scripts and source already downloaded, compiled and ready for somebody to simply jump in and edit kde source code.
I am nearly certain that it does not have to be huge..
Yes, compiling stuff in virtual machines is slower, but in reality we should be able to keep one up to date for new users, and doing an svn update should keep older installs current along... and a lot of it wont need to be recompiled or updated in the virtual machine because the changes will be small.
The download file will be rather large, however compression should be able to find patterns between intermediate objects and the final products, so hopefully a compressed copy will only be a kde install larger than kde+source -- User:AaronPeterson