Bug 273247

Summary: Delete old profiles after performing director install
Product: [Eclipse Project] PDE Reporter: Andrew Niefer <aniefer>
Component: BuildAssignee: pde-build-inbox <pde-build-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: ECOMAR
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Andrew Niefer CLA 2009-04-22 09:38:50 EDT
When doing the director install for product builds, we end up getting several .profile files.  The first few of these represent beginning or intermediate states from before the product was installed and they are not functioning installs.

We should automatically delete all the .profile files except for the last one.  This will prevent these profiles showing up in the revert dialog and allowing the user to revert to a state that won't run.
Comment 1 Lars Vogel CLA 2018-12-03 09:13:01 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 2 Lars Vogel CLA 2018-12-03 09:13:22 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 3 Eclipse Genie CLA 2020-11-25 11:50:02 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2022-11-16 11:54:55 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.