[gentoo-dev] Re: News item: upgrading to Plasma 5

Michael Palimaka posted on Mon, 04 Apr 2016 05:23:03 +1000 as excerpted: > The default in KDE 4 was KDM, with lightdm and sddm also supported. > > We included information about migrating away from KDM because it's no > longer developed or supported and in some cases fails to work with > Plasma 5

[gentoo-portage-dev] [PATCH] emerge: add --search-fuzzy and --search-fuzzy-cutoff options (bug 65566)

Add --search-fuzzy option, with adjustable similarity ratio cutoff that defaults to 0.8 (80% similarity). X-Gentoo-bug: 65566 X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=65566 --- man/emerge.1 | 13 - pym/_emerge/actions.py | 6 -- pym/_emerge/main.py

Re: [gentoo-dev] [PATCH v1 1/3] general-concepts/herds-and-projects: update per GLEP 67 #572144 #549490

On 04/04/16 05:57, NP-Hardass wrote: > On 04/04/2016 12:34 AM, Göktürk Yüksek wrote: >> +sufficient for adding or removing a developer. Note that >> different +projects have different requirements and procedures for >> recruiting +developers, which may require prior arrangements to be >> made

Re: [gentoo-dev] [PATCH v1 1/3] general-concepts/herds-and-projects: update per GLEP 67 #572144 #549490

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/04/2016 12:34 AM, Göktürk Yüksek wrote: > +sufficient for adding or removing a developer. Note that > different +projects have different requirements and procedures for > recruiting +developers, which may require prior arrangements to be >

[gentoo-dev] [PATCH v1 1/3] general-concepts/herds-and-projects: update per GLEP 67 #572144 #549490

The changes are: - Rename the title to "Projects and Herds" to put the emphasis on projects - Explain projects and subprojects in a new "Projects" section - Add a subsection for starting new projects - Add a subsection for joining/leaving a project - Put a warning label at the beginning of the

[gentoo-dev] [PATCH v1 3/3] ebuild-writing/misc-files/metadata: rewrite the section per GLEP 67 #572144

A major rewrite of the section. Here is a brief summary of changes: - Remove the information about the tag per GLEP 67 - Restructure the section in the following order: - metadata.xml syntax - package metadata - metadata examples - maintainer-needed - category metadata - Update the

[gentoo-dev] [PATCH v1 2/3] ebuild-maintenance: s/herd/project/ per GLEP 67 #572144

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=572144 Signed-off-by: Göktürk Yüksek --- ebuild-maintenance/text.xml | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml index

[gentoo-dev] [PATCH v1 0/3] devmanual: update the docs per GLEP 67

Hi, This is the first iteration of the patch series for updating devmanual per GLEP 67. It replaces any reference to herds, includes a major rewrite of the section that explains the metadata.xml file, and talks about how projects are created and managed through the wiki. The section about herds

Re: [gentoo-dev] CVS headers in ebuilds

On 4 April 2016 at 14:43, Robin H. Johnson wrote: > We'd have to find all of those files and explicitly create .gitattribute > files, per directory, for them. I was under the impression that a .gitattribute file in the root directory sufficed? ( I maybe have misinterpreted

Re: [gentoo-dev] CVS headers in ebuilds

On Mon, Apr 04, 2016 at 09:03:59AM +1200, Kent Fredric wrote: > On 4 April 2016 at 08:57, Ulrich Mueller wrote: > > Does anyone still use the CVS $Id$ keywords that are in all ebuilds' > > headers, or are they being expanded anywhere? Or is there any other > > reason why they

[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2016-04-03 23:59 UTC

-sound/xmp 20160401-03:02 bman 0fcb1a6 net-mail/perdition 20160401-03:04 bman f4eb7ab sci-biology/readseq 20160403-21:40 chewi c07656a www-apps/dragonflycms20160401-02:59 bman 126a7d8 www-apps

Re: [gentoo-dev] CVS headers in ebuilds

On Sun, Apr 3, 2016 at 4:57 PM, Ulrich Mueller wrote: > Does anyone still use the CVS $Id$ keywords that are in all ebuilds' > headers, or are they being expanded anywhere? Or is there any other > reason why they should be kept? > > In fact, the council had already voted to drop

Re: [gentoo-dev] CVS headers in ebuilds

On Sun, Apr 3, 2016 at 5:57 PM, William Hubbs wrote: > On Mon, Apr 04, 2016 at 09:03:59AM +1200, Kent Fredric wrote: >> On 4 April 2016 at 08:57, Ulrich Mueller wrote: >> > Does anyone still use the CVS $Id$ keywords that are in all ebuilds' >> > headers, or

[gentoo-dev] Last-rites: dev-java/java-config-wrapper

# James Le Cuirot (03 Apr 2016) # Legacy migration package that is no longer needed. See # bug #549508. Removal in 30 days. dev-java/java-config-wrapper -- James Le Cuirot (chewi) Gentoo Linux Developer pgpcejKQSNaW0.pgp Description: OpenPGP digital signature

Re: [gentoo-dev] CVS headers in ebuilds

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/03/2016 02:57 PM, William Hubbs wrote: > On Mon, Apr 04, 2016 at 09:03:59AM +1200, Kent Fredric wrote: >> On 4 April 2016 at 08:57, Ulrich Mueller wrote: >>> Does anyone still use the CVS $Id$ keywords that are in all >>>

Re: [gentoo-dev] News item: upgrading to Plasma 5

On Mon, Apr 04, 2016 at 03:34:07AM +1000, Michael Palimaka wrote: > Hi, > > KDE team intends to stabilise Plasma 5 shortly, so please review the > accompanying news items. > > Regards, > > Michael > > Title: KDE Plasma 5 Upgrade > Author: Michael Palimaka >

Re: [gentoo-dev] CVS headers in ebuilds

On Mon, Apr 04, 2016 at 09:03:59AM +1200, Kent Fredric wrote: > On 4 April 2016 at 08:57, Ulrich Mueller wrote: > > Does anyone still use the CVS $Id$ keywords that are in all ebuilds' > > headers, or are they being expanded anywhere? Or is there any other > > reason why they

Re: [gentoo-dev] CVS headers in ebuilds

On 4 April 2016 at 08:57, Ulrich Mueller wrote: > Does anyone still use the CVS $Id$ keywords that are in all ebuilds' > headers, or are they being expanded anywhere? Or is there any other > reason why they should be kept? Last time this came up, a sole example case was

[gentoo-dev] CVS headers in ebuilds

Does anyone still use the CVS $Id$ keywords that are in all ebuilds' headers, or are they being expanded anywhere? Or is there any other reason why they should be kept? In fact, the council had already voted to drop them in its 20141014 meeting: Can we drop CVS headers post-migration? Aye:

[gentoo-dev] Re: News item: upgrading to Plasma 5

On 04/04/16 05:06, Rich Freeman wrote: > On Sun, Apr 3, 2016 at 1:34 PM, Michael Palimaka > wrote: >> >> If you normally use KDM to launch Plasma, note that it is no longer >> supported. >> Upstream recommends x11-misc/sddm instead which is pulled in by >> plasma-meta by

[gentoo-dev] Re: News item: upgrading to Plasma 5

On 04/04/16 04:48, Mike Gilbert wrote: > On Sun, Apr 3, 2016 at 1:34 PM, Michael Palimaka > wrote: >> Hi, >> >> KDE team intends to stabilise Plasma 5 shortly, so please review the >> accompanying news items. > > Very exciting, nice work! > >> If you normally use KDM to

Re: [gentoo-dev] News item: upgrading to Plasma 5

On Sun, Apr 3, 2016 at 1:34 PM, Michael Palimaka wrote: > > If you normally use KDM to launch Plasma, note that it is no longer > supported. > Upstream recommends x11-misc/sddm instead which is pulled in by > plasma-meta by > default. To switch, edit /etc/conf.d/xdm and

[gentoo-dev] Re: News item: upgrading to Plasma 5

On 04/04/16 04:34, Ulrich Mueller wrote: >> On Mon, 4 Apr 2016, Michael Palimaka wrote: > >> News-Item-Format: 1.0 >> Display-If-Installed: kde-base/plasma-workspace:4 > > Slot dependencies in Display-If-Installed are not allowed in news item > format 1.0. You should use format 2.0 (which

Re: [gentoo-dev] News item: upgrading to Plasma 5

On Sun, Apr 3, 2016 at 1:34 PM, Michael Palimaka wrote: > Hi, > > KDE team intends to stabilise Plasma 5 shortly, so please review the > accompanying news items. Very exciting, nice work! > If you normally use KDM to launch Plasma, note that it is no longer > supported. >

Re: [gentoo-dev] News item: upgrading to Plasma 5

> On Mon, 4 Apr 2016, Michael Palimaka wrote: > News-Item-Format: 1.0 > Display-If-Installed: kde-base/plasma-workspace:4 Slot dependencies in Display-If-Installed are not allowed in news item format 1.0. You should use format 2.0 (which allows EAPI 5 dependency specifications) if you need

[gentoo-dev] News item: upgrading to Plasma 5

Hi, KDE team intends to stabilise Plasma 5 shortly, so please review the accompanying news items. Regards, Michael Title: KDE Plasma 5 Upgrade Author: Michael Palimaka Content-Type: text/plain Posted: 2016-04-02 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: