First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 14395
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Matthew Kennedy (RETIRED) <mkennedy@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Douglas Pollock <douglas.pollock@magma.ca>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
netbeans-3.4.1.ebuild Ebuild for NetBeans (v3.4.1) text/plain Douglas Pollock 2003-01-22 16:47 0000 3.28 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 14395 depends on: Show dependency tree
Bug 14395 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-01-22 16:46 0000 
This is a new release from the NetBeans people.  It fixes a bunch of bugs, but
doesn't really provide new functionality.

Upgrading to a new NetBeans does not carry over the globally-installed modules
from the previous release.  This is maybe a weakness of the ebuild itself.  If
you were interested, I could write/test an ebuild that would attempt to carry
over the installed modules.

------- Comment #1 From Douglas Pollock 2003-01-22 16:47:22 0000 ------- 
Created an attachment (id=7539) [details]
Ebuild for NetBeans (v3.4.1)

Does not handle migration of installed modules.

------- Comment #2 From Matthew Kennedy (RETIRED) 2003-01-23 00:46:36 0000 ------- 
thanks. updated portage to 3.4.1.  it sounds like your idea to create a better
ebuild that saves a users global netbeans module set is a good idea. if you
develop such a thing, create a new bug report so that we may add it to portage.

matt
First Last Prev Next    No search results available      Search page      Enter new bug