On Fri, Feb 15, 2019 at 9:36 PM Eli Young wrote:
> > I'd still consider this on case by case basis instead of developing a
> general
> > solution, sometimes a simple Recommends works. Sometimes, it's more
> complicated.
>
> That's fair and makes a lot of sense. I do like the pattern mentioned by
> I'd still consider this on case by case basis instead of developing a general
> solution, sometimes a simple Recommends works. Sometimes, it's more
> complicated.
That's fair and makes a lot of sense. I do like the pattern mentioned by Igor
as used for Rust packages of using + as a separator
On 2/5/19 12:44 AM, Eli Young wrote:
Python packages can specify extras dependencies, which are sets of dependencies not
required for core functionality, and which generally correspond to some feature. These
can then be specified by downstream consumers of the package. For example, requests has
In Rust we have similar problem (we have "features" than "extras") and we
always package them as a subpackages.
https://src.fedoraproject.org/rpms/rust-serde/blob/master/f/rust-serde.spec
rust-serde-devel
rust-serde+alloc-devel
rust-serde+default-devel
rust-serde+derive-devel
rust-serde+rc-devel
r
On 05. 02. 19 0:44, Eli Young wrote:
Python packages can specify extras dependencies, which are sets of dependencies not
required for core functionality, and which generally correspond to some feature. These
can then be specified by downstream consumers of the package. For example, requests has
Python packages can specify extras dependencies, which are sets of dependencies
not required for core functionality, and which generally correspond to some
feature. These can then be specified by downstream consumers of the package.
For example, requests has an entry in extras called security[1]
