Closed Bug 658322 Opened 15 years ago Closed 15 years ago

Use elmo-lib as a submodule in vendor-local

Categories

(Webtools Graveyard :: Elmo, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: stas, Assigned: stas)

References

Details

Attachments

(1 file)

The advantages would be: - we can easily add other non-compiled dependencies to vendor - we don't risk that upstream changes to playdoh-lib break our code when we do 'git submodule update'
Assignee: nobody → stas
Status: NEW → ASSIGNED
Priority: -- → P2
Here's another idea: - leave playdoh-lib in vendor/ - add elmo-lib in vendor-local/ (which has precedence in manage.py)
Here a patch implementing the vendor-local approach. I created https://github.com/mozilla/elmo-lib, too. I edited the update_script.py script to entirely rely on --recursive. I don't think it's a good think to do 'git pull' inside the vendor[-local] submodule manually, as that can pull in more recent commits than the one registered as the submodule. That looks lke a playdoh bug to me.
Attachment #535239 - Flags: review?(peterbe)
Blocks: 548298
Attachment #535239 - Flags: review?(peterbe) → review+
Pushed: https://github.com/mozilla/elmo/commit/c588fe2174b4d644d202cf596fb41cadd226c0dd Please pull with `git pull && git submodule update --init --recursive`
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.2
Adjusting the summary to what has been done.
Summary: Use elmo-lib instead of playdoh-lib for vendor/ → Use elmo-lib as a submodule in vendor-local
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: