Closed
Bug 304505
Opened 19 years ago
Closed 19 years ago
bootstrap and modules in client.mk should list specific modules and files
Categories
(Minimo Graveyard :: Build Config, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: chase, Assigned: benjamin)
Details
(Keywords: fixed1.8)
Attachments
(1 file)
1.13 KB,
patch
|
chase
:
review+
|
Details | Diff | Splinter Review |
The minimo project in client.mk should list specific modules and files for its BOOTSTRAP and MODULES sections. Currently, a CVS error of '... this file is in the way' when someone attempts to checkout the minimo or all projects. This problem exists on the Mozilla 1.8 branch and trunk. Benjamin, this is the likely cause of why I couldn't pull by date from the trunk earlier today.
Comment 1•19 years ago
|
||
vlad is testing a patch. This needs to be fixed on both the trunk and the branch.
Reporter | ||
Comment 2•19 years ago
|
||
See related bug 304504.
Assignee | ||
Comment 3•19 years ago
|
||
This seems really simple to me... why use BOOTSTRAP_minimo at all?
Comment 4•19 years ago
|
||
I use it because I have a mozconfig file in : mozilla/minimo/config/mozconfig/
Assignee | ||
Updated•19 years ago
|
Priority: -- → P1
Assignee | ||
Comment 5•19 years ago
|
||
doug, if you really need to check out those mozconfig files during bootstrap, we should list the mozilla/minimo/config/mozconfig/* files individually in BOOTSTRAP_minimo and mozilla/minimo in MODULES_minimo.
Reporter | ||
Comment 6•19 years ago
|
||
(In reply to comment #5) > doug, if you really need to check out those mozconfig files during bootstrap, we > should list the mozilla/minimo/config/mozconfig/* files individually in > BOOTSTRAP_minimo and mozilla/minimo in MODULES_minimo. I agree, this is probably what dougt wants.
Comment 7•19 years ago
|
||
The problem is that list might grow overtime. Why can't we just pull a directory?
Reporter | ||
Updated•19 years ago
|
Attachment #192826 -
Flags: review?(chase) → review+
Reporter | ||
Comment 8•19 years ago
|
||
(In reply to comment #7) > The problem is that list might grow overtime. Why can't we just pull a directory? Is that really a big problem? If the list grows over time we adding to it won't be that hard, or if it does get difficult look at pulling the config/ directory itself. I'd like for us to fix this on the branch and trunk (wherever it's not already fixed) soon so I can pull the 'all' project by-date for tagging.
Comment 9•19 years ago
|
||
sure, i don't really care which way you go; however I am confused why you can pull a directory in bootstrap.
Assignee | ||
Comment 10•19 years ago
|
||
This was already fixed on branch. I just checked in trunk to make it match the branch. Doug, feel free to add the indivdual mozconfig files to BOOTSTRAP_minimo as needed. The reason you can't checkout a directory during the bootstrap phase is that the sticky-date gets set on the directory in a way that confuses CVS.
You need to log in
before you can comment on or make changes to this bug.
Description
•