On 12/06/2020 18:24, Georgy Yakovlev wrote:
On 6/12/20 4:16 AM, Luca Barbato wrote:
On 12/06/2020 11:04, Georgy Yakovlev wrote:
+# cargo_src_configure --no-default-features
Shall we default in not-defaulting so we can spare some boilerplate?
I don't think so. Let me explain.
First of all, this will force to explicitly micro-manage all the
features for all the packages in the tree.
The idea is:
- if myfeatures is empty, do not pass --no-default-features.
- if myfeatures has content, automatically pass --no-default-features.
--no-default-features --features default seems working as intended btw.
lu
