Summary: | net-mail/isync: 1.2.0 Version Bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aaron W. Swenson <titanofold> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alonbl, fabrizio.fabbri, willikyl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
updated ebuild with sasl/ssl/compat additional flags
isync-1.2.0.ebuild.diff |
Description
Aaron W. Swenson
2015-05-02 15:54:53 UTC
Created attachment 403236 [details]
updated ebuild with sasl/ssl/compat additional flags
I just attached a ebuild with sasl/ssl/zlib/compat additional flag supported by the autoconfiscated package. The way I'm reading this: $(use_enable !compat compat) The compatibility wrapper will be included when the compat use flag is disabled. This doesn't seem natural. Sorry for the confusion but it's the first time that I played with an ebuild and I'm still learning. The configure option is "--disable-compat" so by default look enabled. I tried with $(use_enable compat) but the result was that emerge was saying "-compat" and the configure was called with "--disable-compat" So "$(use_enable !compat compat)" was for that, but yeah it's quite not natural. :) f. I gave your ebuild a go, and the compat handling is inversed. When the user wants the isync compatibility wrapper they should enable the compat use flag. When they don't want it, being deprecated and all, they should disable the use flag. Additionally, we'll want to say what compat will enable in this package. [1] If you have any questions, just email me and I'll be happy to assist you. [1] https://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/ Created attachment 403504 [details, diff]
isync-1.2.0.ebuild.diff
*** Bug 485426 has been marked as a duplicate of this bug. *** net-mail: any objection to comment this? work for me. Added. |