I think USE flags are more appropriate for library features (which is exactly the way portage uses them). So you have your rust app with conditional code that depends on a particular cfg ( https://github.com/mozilla/rust/wiki/Doc-attributes) and then you expose a list of these in your package specification so that others can know to say - I use the json library but with built-in URI support.
On Sat, Feb 1, 2014 at 3:45 PM, Lee Braiden <[email protected]> wrote: > On 01/02/14 14:49, Vladimir Lushnikov wrote: > >> Portage has a very similar syntax/way of specifying runtime vs. >> build-time dependencies: http://devmanual.gentoo.org/ >> general-concepts/dependencies/. >> >> Apt doesn't have support for slots and USE flags (code that is >> included/excluded at compile time for optional features). >> >> > Agreed; use flags are very nice :) I find them a bit clunky / breakable, > though -- it's very hard to know what the valid range of flags is, and how > that will affect every package on your system. If Rust gets something > similar, the exact circumstances under which they're used, the range valid > values, and the effects of each, should be EXTREMELY clear. > > > -- > Lee > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
