Archives
Archives
| From: | Michael Orlitzky <mjo@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] Re: version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass | ||
| Date: | Mon, 22 Jan 2018 15:04:51 | ||
| Message-Id: | a00afe57-024a-77f8-2dc2-814d892a0e83@gentoo.org | ||
| In Reply to: | [gentoo-dev] Re: version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass by Duncan <1i5t5.duncan@cox.net> | ||
| 1 | On 01/22/2018 05:10 AM, Duncan wrote: |
| 2 | >>> |
| 3 | >>> If the dependencies are to remain in the eclasses, then the eclasses |
| 4 | >>> should get a new revision when those dependencies change. Afterwards, |
| 5 | >>> the consumers can be revbumped and stabilized normally to utilize the |
| 6 | >>> new eclass. |
| 7 | >> |
| 8 | >> Sounds good! |
| 9 | > |
| 10 | > How does that work with live-vcs ebuilds, aka -9999 ebuilds? |
| 11 | > |
| 12 | |
| 13 | It doesn't. As with upstream code changes, you have to figure out |
| 14 | yourself when it's time to re-emerge a live ebuild. |
| Subject | Author |
|---|---|
| [gentoo-dev] Re: version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass | Duncan <1i5t5.duncan@×××.net> |