This is a tracker bug. Netbeans 6.1 should be released in March. Latest ebuild is in java-experimental overlay. Currently it is p.mask'd. Atm, only netbeans platform and 'harness' clusters compile without problem and without bundled stuff (except tomcat-webserver-3.2.jar which we do not plan to unbundle). Currently I work on 'ide' cluster, and dev-java/netbeans-svnclientadapter needs to be packaged now. Path to ebuild in java-experimental overlay: http://overlays.gentoo.org/proj/java/browser/java-experimental/dev-util/netbeans Only ebuilds >= netbeans-6.1_alpha20080127134700 are the newest ones, previous ebuilds are still based on CVS repository. The latest ebuild is based on mercurial repository (netbeans moved from CVS to mercurial few weeks ago). Any help, especially with packaging needed deps and testing is appreciated.
Now netbeans-6.1 with all the bundled stuff is available in java-experimental overlay. No p.masking is applied now. All netbeans clusters are buildable atm. I need to unbundle the jars now.
Could 6.1 -please- finally be moved into the main portage tree?
(In reply to comment #2) > Could 6.1 -please- finally be moved into the main portage tree? > Yes, please - 6.1 has been out for a couple of months. Is there any chance that 6.1 will be moved into the main portage tree this year or do I have to install it directly from netbeans.org? (Using java-experimental is not an option for a couple of reasons). Thanks in advance, Mark
(In reply to comment #3) > (In reply to comment #2) > > Could 6.1 -please- finally be moved into the main portage tree? > > > > Yes, please - 6.1 has been out for a couple of months. > > Is there any chance that 6.1 will be moved into the main portage tree this year > or do I have to install it directly from netbeans.org? (Using java-experimental > is not an option for a couple of reasons). > > Thanks in advance, > Mark > If that would be that easy, nb 6.1 would already be in tree. I'd suggest you install nb from upstream, it will take some time to get nb 6.1 to tree and I am the only developer working on this ebuild and currenty short of time.
(In reply to comment #4) > If that would be that easy, nb 6.1 would already be in tree. I'd suggest you > install nb from upstream, it will take some time to get nb 6.1 to tree and I am > the only developer working on this ebuild and currenty short of time. Ah, thanks. I didn't mean to wind you up - just wanted to know if makes sense to install it from upstream :-) (In fact, installing it via netbeans org did work very well - I haven't encountered any problem). Thanks for your work, Mark
I am very concerened about maintaining a 'clean' system. Can anyone tell me what problems I might experience with and upstream installation?
Can't you use the ebuild from overlay? Worked fine for me. Only problems with upstream install that I can imagine are: - not met dependences as they are not installed automatically - netbeans binaries being compiled against other versions of libraries than you use, but as others successfully used it, it shouldn't be a problem - higher chance that something will be left when you remove this package
(In reply to comment #7) > Can't you use the ebuild from overlay? Worked fine for me. Didn't work fine with me :-( Whenever I tried to open a new project, netbeans (from overlay) crashed. > - not met dependences as they are not installed automatically No problem at all > - netbeans binaries being compiled against other versions of libraries than you > use, but as others successfully used it, it shouldn't be a problem Yup - again: no problem. > - higher chance that something will be left when you remove this package Nope: when you install netbeans from upstream, it installs itself in $HOME/netbeans-6.1. The system itself isn't touched in any way. Removing it should be piece of cake: rm -rf $HOME/netbeans-6.1 There's a distinct advantage installing it from upstream which I haven't considered before: Since netbeans is able to update parts of itself, it's *very* convenient to do so (since all files reside in your home directory). If installed via portage this isn't so easy - because in *that* case root owns netbeans and one has to run netbeans as root to upgrade (which isn't a very good idea). The drawback: it's only installed for one user (instead of system wide). I can live with that - in fact, I like the update feature so much I won't install netbeans via portage, even if it's available.
(In reply to comment #8) > ... > There's a distinct advantage installing it from upstream which I haven't > considered before: > > Since netbeans is able to update parts of itself, it's *very* convenient to do > so (since all files reside in your home directory). If installed via portage > this isn't so easy - because in *that* case root owns netbeans and one has to > run netbeans as root to upgrade (which isn't a very good idea). > ... I don't agree with this. AFAIK, netbeans can either install the updates as shared (that's really not possible in gentoo because of the root permissions) or locally just for the user running netbeans. So even if you install netbeans using ebuild, you can install new plugins and upgrade older ones.
Yup, installing it from upstream puts it as far as I see cleanly in ~/netbeans-x.x This is completly sufficent for me, keeps my system clean anyways. For any single-user system I would recommend the upstream installation.
Any chance 6.1 is going to wind up in the main gentoo repository soon?
No, but you can expect netbeans 6.5 being in tree in the second half of November if everything goes well.
netbeans 6.5 is in the main tree, you are encouraged to use it instead of netbeans 6.1. I removed netbeans 6.1 from overlay as it is obsoleted by netbeans 6.5.
