Issue 4177 - sysui directories duplicated in CVS
Summary: sysui directories duplicated in CVS
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 641
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: khendricks
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-22 16:03 UTC by chris
Modified: 2003-02-24 14:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description chris 2002-04-22 16:03:43 UTC 
chris@shawn:/usr/local/src/ooffice/x$ cvs get -r OOO_STABLE_1 sysui
[...]
chris@shawn:/usr/local/src/ooffice/x$ ls sysui
CVS  java  oounix  oowin32  prj  source  tools  unix  util  win32

As far as I understand, sysui/unix was renamed sysui/oounix, and the same for
win32.  But the tag was never deleted on the old directories.
Comment 1 khendricks 2002-04-22 17:21:50 UTC 
Hi,

No they are not exact duplicates.  Please don't delete or remove 
either.

I create the oowin32 and the oounix to help work on desktop 
integration for linux/unix (kde / gnome) and to help integrate new 
icons just for OOo 1.0.

The prj/build.lst now builds them, but they have not been completely 
tested under all circumstances so I wanted to keep the previous 
versions around unix and win32 so that they could be used for 
reference and just in case we had to revert.

So please do not remove them yet.  Keep them.

Thanks,

Kevin
Comment 2 Martin Hollmichel 2002-04-22 17:28:30 UTC 
resetting ooo1.0, as kevin explained this is not a key issue for the 
1.0 release. 
kevin, who should be the owner of this issue ?
Comment 3 khendricks 2002-04-22 17:33:45 UTC 
Hi,

Please make me the owner and then after OOo 1.0 is released I will 
double check with Oliver what he wants to have done and take care of 
deleting them if that is what he wants to do.

Thanks,

Kevin

p.s. External issue creators should not be able to set OOO 1.0 
keyword for every minor thing.  This is nothing that needs to be 
looked at for OOo 1.0.

Perhaps there should be a separate or new internal only keyword for 
our use.

Thanks,

Kevin
Comment 4 chris 2002-04-22 18:36:05 UTC 
Sorry Kevin, I tagged it like that because I was refering to
OOO_STABLE_1 CVS.
Comment 5 khendricks 2002-04-22 18:54:24 UTC 
Hi,

Understood.  No problem.  We are using the ooo1.0 keyword to keep 
track of potential showstopper issues that might delay release of 
OOo 1.0 or critical bug fixes that need to make it in.

Almost duplicate source directories just did not fit that bill!  ;-)

Thanks,

Kevin
Comment 6 khendricks 2002-05-04 13:10:35 UTC 
Hi,

This is not a bug.

Closing this as invalid.

Kevin
Comment 7 chris 2003-02-24 14:12:20 UTC 
Verified & closing