Closed Bug 103249 Opened 23 years ago Closed 22 years ago

move Mac editor projects to corresponding sub-directories

Categories

(SeaMonkey :: Build Config, defect)

PowerPC
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX
mozilla1.3beta

People

(Reporter: sfraser_bugs, Assigned: Brade)

Details

The editor projects are currently in mozilla/editor/macbuild. I suggest we move 
them to mozilla/libeditor/macbuild, and mozilla/composer/macbuild, so keep things 
more self-contained. Comments?
yes please.  It would be nice to grab libeditor from one tree and copy it onto 
another, and know that you got your project tweaks as well...
I agree about the self-containing.
I do notice, when I'm debugging, that I need to load both projects so it is 
certainly more convenient for me to have both in the same directory.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.6
Sorry I haven't gotten to this yet; I'll try to do it next week (assuming I can 
get approval).  Simon already gave me sr= on irc; I assume Joe has given me r= 
implicitly with his comments.
OS: Mac System 8.5 → All
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Summary: Where should the Mac editor projects live? → move Mac editor projects to corresponding sub-directories
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla0.9.9
balancing milestones
Target Milestone: mozilla0.9.9 → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to adt@netscape.com.  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
projects will soon be dead; no point in moving them now :-/
-->WONTFIX
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Target Milestone: mozilla1.2alpha → mozilla1.3beta
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.