Bug 383687 - Adding newly imported projects to the build sequence: consider making it optional
Summary: Adding newly imported projects to the build sequence: consider making it opti...
Status: REPORTED
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (other bugs)
Version First Reported In: unspecified
Platform: Other All
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-19 09:11 UTC by RJVB
Modified: 2017-08-19 09:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2017-08-19 09:11:05 UTC
While my multi-project sessions usually contain related projects it is extremely rare that I have any use for the build sequence feature. If anything it would require me to install through the IDE, which is something I'm very unlikely to consider doing.
It's also a pure coincidence if I import projects in the exact order of dependencies (if anything it's usually the reverse order).

Having projects declared in the build sequence thus interferes with building, and I've made it a habit to remove each newly imported project from the build sequence.

That's 2 unnecessary clicks that are beginning to grow old on me, so I'd like to suggest considering a global option to disable the automatic adding of new projects to the build sequence. Adding them manually also takes 2 clicks.