FS#18732 - [netbeans] don't need whole 400MBs - split package to core and plugins (like Eclipse and others do)

Attached to Project: Community Packages
Opened by Tomas Mudrunka (harvie) - Thursday, 18 March 2010, 07:03 GMT
Last edited by Dan Griffiths (Ghost1227) - Friday, 26 March 2010, 22:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: As you can see on download page: http://netbeans.org/downloads/index.html
netbeans are highly modular and since pacman/makepkg supports building of multiple packages using single pkgbuild, there's no need to have one big BLOATED package of 300-400MB when i need just basic 50MB instalation with basic java SE support.

I need netbeans to school, but my computer is hardly running out of disk space. I also do not want to install netbeans manualy outside of pacman tree - it's not Arch Way.

Other IDE packages in ArchLinux have separated core and separated plugins.

IMHO you can split down all plugins, so ArchLinux's NetBeans will be more modular than that from official instalator.

Steps to reproduce:
1.) pacman -S netbeans
2.) watch that fat package bloating you computer
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Friday, 26 March 2010, 22:46 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See comment
Comment by Tomas Mudrunka (harvie) - Friday, 26 March 2010, 11:49 GMT
BTW there are few editions of netbeans available for download, so i think PKGBUILD should use full bundle and strip it down into more small packages...
Comment by Dan Griffiths (Ghost1227) - Friday, 26 March 2010, 22:46 GMT
We do use the full bundle, but it's not a simple matter of changing a config option... each part of the netbeans suite installs a number of files throughout various parts of the directory tree, and there is no config or install script. Hence, each section of a split package would likely require several hundred lines of removing files from the full package, and even then there's no guarantee it'd work right. I believe this to be not worth the trouble it would cause. If you have a decent split package for this then you are welcome to send it in and I will reconsider the decision. However, I suspect for your purposes it'd probably be more efficient to rebuild the suite from ABS and simply change the source url to reflect whichever part of the suite you require.

Loading...