eselect 1.1 will ship the news-tng news item, so Portage can extend to a any-of dependency: eselect-news or >=eselect-1.1
I second this. But maybe the message in emerge should be changed then: Use "eselect news" or "eselect news-tng" to read news items.
I added the dependency now that eselect 1.1.1 is going stable. Ulrich, is a mapping of eselect news to eselect news-tng possible by blocking eselect-news itself?
Is the older eselect-news packages still going to be maintained? If not, maybe we can rename news-tng to news and make the new select block eselect-news.
(In reply to comment #3) > Is the older eselect-news packages still going to be maintained? If not, maybe > we can rename news-tng to news and make the new select block eselect-news. Theoretically it is maintained but it has some little usability flaws that ulm addressed. Let's ask the maintainer. Piotr, I don't know if you had a look at the news-tng eselect module, but it is superior to the original news module. Is there still development going on or can we move it into the eselect core?
(In reply to comment #4) > [...] can we move it into the eselect core? To clarify: We cannot include the original news module in eselect since (being part of Paludis) it doesn't have a Gentoo copyright assignment. Renaming of news-tng to news (as suggested by Zac) would be possible of course.
Would you have any objections against the following plan: 1. In eselect proper, rename news-tng.eselect to news.eselect 2. Change the eselect-news dependency in the portage and paludis ebuilds to: || ( >=app-admin/eselect-1.2 >=app-admin/eselect-news-20071201 ) 3. Release app-admin/eselect-1.2, blocking against app-admin/eselect-news Adding gentoofan23 to CC (as paludis ebuild maintainer).
(In reply to comment #6) > 1. In eselect proper, rename news-tng.eselect to news.eselect > 2. Change the eselect-news dependency in the portage and paludis ebuilds to: > || ( >=app-admin/eselect-1.2 >=app-admin/eselect-news-20071201 ) > 3. Release app-admin/eselect-1.2, blocking against app-admin/eselect-news All done in eselect-1.2_rc1.
Reopening, because Portage still depends on eselect-1.1, not 1.2. The dependency in Paludis is now >=app-admin/eselect-1.2 (no eselect-news), and it should be changed to the same for Portage, too.
<ulm> zmedico: ok with you if I update the eselect dependency in sys-apps/portage-2.2*? bug 271447 <Willikins> ulm: https://bugs.gentoo.org/271447 "Change dependency for GLEP 42 news module"; Portage Development, Core - External Interaction; REOP; fauli@g.o:eselect@g.o <ulm> portage-2.1* would follow after eselect-1.2* stabilisation <zmedico> ulm: yes, please do <ulm> k <zmedico> thanks Done for sys-apps/portage-2.2*.
*** Bug 287756 has been marked as a duplicate of this bug. ***
Done for portage-2.1.6* too, following stabilisation of eselect-1.2.3.