Bug 1604376 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Gathering a few notes in case it turns out to be something I could mentor.

1. Create a C++ XPCOM component that implements `nsICommandLineHandler` and does what is mentioned in comment 0.
2. Register said XPCOM component as a command-line handler.
3. How can we unit/integration test this?
Gathering a few notes in case it turns out to be something I could mentor.

1. Create a C++ XPCOM component that implements `nsICommandLineHandler` and does what is mentioned in comment 0:
    1. Create a temporary directory;
    2. Use that directory;
    3. Cleanup the directory upon exit.
2. Register said XPCOM component as a command-line handler.
3. How can we unit/integration test this?
4. How do we ensure that the directory is cleaned up even in case of crash?
Gathering a few notes in case it turns out to be something I could mentor.

1.  Extend `nsToolkitProfileService::SelectStartupProfile` to handle a new option `--temp-profile` to:
    1. Create a temporary directory;
    2. Use that directory;
    3. Cleanup the directory upon exit. <-- This is probably the difficult part.
2. Register said XPCOM component as a command-line handler.
3. How can we unit/integration test this?
4. How do we ensure that the directory is cleaned up even in case of crash?
Gathering a few notes in case it turns out to be something I could mentor.

1.  Extend `nsToolkitProfileService::SelectStartupProfile` to handle a new option `--temp-profile` to:
    1. Create a temporary directory;
    2. Use that directory;
    3. Cleanup the directory upon exit. <-- This is probably the difficult part.
2. How can we unit/integration test this?
3. How do we ensure that the directory is cleaned up even in case of crash?

Back to Bug 1604376 Comment 5