Bug 1584567 Comment 1 Edit History

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

So turns out I was wrong. This doesn't cause us to invoke configure and it has nothing to do with bug 1580280.

But before I realized this, I went ahead and implemented the patches to fix this. I'd still prefer to get them landed as I think `conditional_names` can be a little problematic (breaks assumptions by changing the names of commands at runtime).

However, these patches aren't solving any current problems. So if they cause problems or pose risk I'm happy to abandon them.
So turns out I was wrong. This doesn't cause us to invoke configure and it has nothing to do with bug 1580280.

But before I realized this, I went ahead and implemented the patches to fix it. I'd still prefer to get them landed as I think `conditional_names` can be a little problematic (breaks assumptions by changing the names of commands at runtime).

However, these patches aren't solving any current problems. So if they cause problems or pose risk I'm happy to abandon them.
So turns out I was wrong. This doesn't cause us to invoke configure and it has nothing to do with bug 1580280.

But before I realized this, I went ahead and implemented the patches to fix it. I'd still prefer to get them landed as I think `conditional_names` can be problematic (breaks assumptions by changing the names of commands at runtime). Mach is simpler and cleaner without them.

However, these patches aren't solving any current problems. So if they cause problems or pose risk I'm happy to abandon them.

Back to Bug 1584567 Comment 1