Re: [gentoo-dev] The future of virtual/mysql and virtual/libmysqlclient

On Tue, Feb 13, 2018 at 09:32:32PM -0500, Brian Evans wrote: > I have a plan I would like some eyes on... > > I want to gradually *BAN* the use of virtual/mysql and > virtual/libmysqlclient as dependencies. Overall I agree, but there's some slight concerns I have. > To accomplish this, force

[gentoo-dev] The future of virtual/mysql and virtual/libmysqlclient

I have a plan I would like some eyes on... I want to gradually *BAN* the use of virtual/mysql and virtual/libmysqlclient as dependencies. To accomplish this, force dev-db/mysql-connector-c to be the only souce of libmysqlclient.so. Packages that choose to support libmariadb.so instead can

Re: [gentoo-dev] newsitem: baselayout 2.5 changes (round 2)

William Hubbs wrote: > The first change is that ROOTPATH is no longer set. This means all of > the *sbin directories will be added to the default path for all users > instead of just the root user. Maybe add a sentence about why this is changing or even neccessary, to avoid perception of weakened

[gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

> On Tue, 13 Feb 2018, Ulrich Mueller wrote: > [about QA's role] Sorry, I didn't spend attention to the fact that the message I was replying to was in the wrong list. Please continue in gentoo-project where this thread belongs. pgp8a3bnmBxzU.pgp Description: PGP signature

[gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

> On Tue, 13 Feb 2018, Chí-Thanh Christopher Nguyễn wrote: > Dean Stephens schrieb: >>> QA and Comrel are special in that they can take disciplinary >>> action against non-members, which there is no recourse against >>> except appeal to the Council. >>> >> At the very least: QA, Comrel, IRC

[gentoo-dev] Gentoo has been accepted as a Google Summer of Code 2018 mentoring organization

Hello everyone, Gentoo has been accepted into the Google Summer of Code 2018! Mentors: If you want to mentor some projects on Gentoo GSoC 2018 please add yourself here [1] as soon as possible, is important!. Someone from the Gentoo GSoC team will contact you back, as soon as possible. Students:

Re: [gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

On 13/02/18 20:57, Rich Freeman wrote: > On Tue, Feb 13, 2018 at 3:53 PM, Chí-Thanh Christopher Nguyễn > wrote: >> Dean Stephens schrieb: >> Suppose that the council decides to accept an appeal from comrel. Is it a conflict of interest for a member of the council

Re: [gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

On Tue, Feb 13, 2018 at 3:53 PM, Chí-Thanh Christopher Nguyễn wrote: > Dean Stephens schrieb: > >>> Suppose that the council decides to accept an appeal from comrel. Is it >>> a conflict of interest for a member of the council who is also a member >>> of comrel to vote in the

[gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

Ulrich Mueller schrieb: > Don't vote for that person then? Why would we need a general rule > restricting voters from electing any specific candidate? For the same reason why governing bodies sometimes restrict accumulation of mandates (and have term limits etc.). Of course the electorate can

[gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

Dean Stephens schrieb: >> Suppose that the council decides to accept an appeal from comrel. Is it >> a conflict of interest for a member of the council who is also a member >> of comrel to vote in the appeal? If it isn't, it is at least a pretty >> strong perception that it is. >> > Why? How?

[gentoo-dev] Re: [gentoo-project] rfc: council members and appeals

Dean Stephens schrieb: >> QA and Comrel are special in that they can take disciplinary action against >> non-members, which there is no recourse against except appeal to the Council. >> > At the very least: QA, Comrel, IRC ops (in every project specific > channel), planet/universe, forums, and

[gentoo-dev] Re: SAT-based dependency solver: request for test cases

Michael Lienhardt wrote: > the criteria list you gave (maybe it's in the PMS) I doubt that it is in PMS, and IMHO it also does not belong there: As long as the result configuration is valid (no collisions or unresolvable loops) all should be equally fine from the

Re: [gentoo-dev] Re: SAT-based dependency solver: request for test cases

Thanks a lot for this list! You are totally right, simply translating the dependencies into SAT constraints and feeding them to a solver returns in most cases a very bad, totally useless solution. However, nowadays many solvers support solution optimization, i.e., you can specify an ordered

Re: [gentoo-dev] Re: Lastrite: app-crypt/monkeysign

On 02/13/2018 11:47 AM, Michael Palimaka wrote: > On 02/12/2018 08:59 AM, Kristian Fiskerstrand wrote: >> # Kristian Fiskerstrand (11 Feb 2018) >> # Lastrite: app-crypt/monkeysign . Please use caff from >> # app-crypt/signing-party instead. Removal in 30 days. >> # Bug: #647352

[gentoo-dev] Re: SAT-based dependency solver: request for test cases

Michał Górny wrote: >> >> d. In || ( ... ) clauses the left-most packages should be preserved. s/preserved/preferred/ > you've missed the most important point: we want to prefer > the newest version, whenever possible > ;-). Yes, you are right: I had thought only about

Re: [gentoo-dev] Re: Lastrite: app-crypt/monkeysign

On 13/02/18 10:47, Michael Palimaka wrote: > On 02/12/2018 08:59 AM, Kristian Fiskerstrand wrote: >> # Kristian Fiskerstrand (11 Feb 2018) >> # Lastrite: app-crypt/monkeysign . Please use caff from >> # app-crypt/signing-party instead. Removal in 30 days. >> # Bug: #647352 >>

[gentoo-dev] Re: Lastrite: app-crypt/monkeysign

On 02/12/2018 08:59 AM, Kristian Fiskerstrand wrote: > # Kristian Fiskerstrand (11 Feb 2018) > # Lastrite: app-crypt/monkeysign . Please use caff from > # app-crypt/signing-party instead. Removal in 30 days. > # Bug: #647352 > app-crypt/monkeysign > What's the reason for the

Re: [gentoo-dev] Re: SAT-based dependency solver: request for test cases

W dniu wto, 13.02.2018 o godzinie 07∶49 +, użytkownik Martin Vaeth napisał: > Michael Lienhardt wrote: > > > > ad-hoc fixes and tweaks that can hardly be encoded into SAT constraints. > > The main difficulty which I see is that one does not want only _some_ >