From nobody Mon Mar 25 20:25:19 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V3PZN2Xcsz4p13b for ; Mon, 25 Mar 2024 20:25:32 +0000 (UTC) (envelope-from sirdice@gmail.com) Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V3PZM4YWwz3yng for ; Mon, 25 Mar 2024 20:25:31 +0000 (UTC) (envelope-from sirdice@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="J/n+P03M"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of sirdice@gmail.com designates 2607:f8b0:4864:20::42e as permitted sender) smtp.mailfrom=sirdice@gmail.com Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-6ea9a60f7f5so1772393b3a.3 for ; Mon, 25 Mar 2024 13:25:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711398329; x=1712003129; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=x1UNfpi2gtn5v75ovOAHbPoIGSucPzXAsT2UfjCaa44=; b=J/n+P03MyD2AH4kEViQPWhsj8qCeWIak4rJgjlnLW3/R1CPKdV7PmD3u7splLxRu68 vHVfJZgmSlYYxJovz+x9UvPbxtJ4PSiwH3RXMQ4keZwwWKpniu0p25Ui+e4aYWuT1AYs 7ohbsdI+WlSABCOc0OYkqyEaVVvTwno09ta/N+Z7knNFirKwCZkZHYgMWSKw3FulG2/v KmGw/NpjmJXaOy0b9SwHiY3+QfvzTX/KqvIE2P9289CYkceF6LyYkB64He8DCDkocp+O fQzQ5LYy/LbTSuQtTqRhuTb4PX1uEiYXT+wVwi6nktqvKUvSzeObNiwg00SVJmElQgXg 3tfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711398329; x=1712003129; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=x1UNfpi2gtn5v75ovOAHbPoIGSucPzXAsT2UfjCaa44=; b=flLQF6HDcL+gyCdvQOggT7zjt9nKm4PgEWRq0ibKoszDV0YzxUgoUwmqh6wkJ5KgQQ V9ujvbX8MjaKr4x0mxqKyEbwFtfwnwbfO37bYVXYKHZYU/p69cTADXPqOwdYAZLmw/ko wncXM0GMn24czMNiIVabYmlR3f2UB7KCJYzOP1Yc6GgQpMg8YwBYQ+cKw3m/5lwKauVP V3EkrOfnb7bYfpMkcuv2B5D6tPjyxFcVKHzn2xwI6NgGBN2yPc/10pIu31kKiSg6R/d8 I3L8rWahplhp8mj8DgYnTGEB95qbjZ+YUamHOUh/nl/vUrDhuLWtHU51wFKTBn8xidnr uNDg== X-Gm-Message-State: AOJu0YyPbGYOYDdWBJYCl+B37KVNEu/Zc4csGU9b8d2sArVfoHVG1tyM wZ/MO6TcIxmrvZ2uYrhlSDLDhA9op3ef+ynSxNOk372bZriQRLetG+Uc1oBeYDUgKTRFDzjT/nx 9aeeFzVASsRwyj8/eGOTTMy02XeQvf4OOEuU= X-Google-Smtp-Source: AGHT+IF4EwXaJfJvY4sGXEUVGehEP78R75WYKpKnBuYC0OcRpJ9qCX+P/ocdZIuK7tU09GNlfrhkP4sgLeswAEviQpc= X-Received: by 2002:a05:6a20:3ca2:b0:1a3:6dbb:f072 with SMTP id b34-20020a056a203ca200b001a36dbbf072mr7620000pzj.8.1711398328888; Mon, 25 Mar 2024 13:25:28 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 From: SirDice Date: Mon, 25 Mar 2024 21:25:19 +0100 Message-ID: Subject: p5-DBD-mysql: Stuck between a rock and a hard place To: freebsd-ports@freebsd.org Content-Type: multipart/alternative; boundary="000000000000767765061481f949" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.83 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.83)[-0.831]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::42e:from] X-Rspamd-Queue-Id: 4V3PZM4YWwz3yng --000000000000767765061481f949 Content-Type: text/plain; charset="UTF-8" All, I took over maintainership of p5-DBD-mysql last week. Apparently I unwittingly managed to poke a hornets nest. Upstream author changed the code to make it only compatible with MySQL 8.x. I've tried patching out some of those changes but it requires quite an effort and is, in the end, unmaintainable. So currently it is broken if you change the default mysql to MariaDB. At the moment I see a couple of options 1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysql4 'legacy' version port. 2) 'downgrade' p5-DBD-mysql to 4.051 and add a p5-DBD-mysql5 'new' version port. #1 works for the default MySQL (still at 8.0) but breaks if trying to build with MariaDB. Arguments are made that those ports should switch to p5-DBD-mariadb instead. But this causes another set of problems, it's not a drop-in replacement and some ports seem to have problems with DBD-MariaDB. Those ports could switch to the 'legacy' version until those issues are resolved upstream. #1 also poses a problem if the default is switched to MariaDB and ports haven't been updated yet to depend on p5-DBD-mariadb or p5-DBD-mysql4. #2 is probably the 'quickest' fix, it restores the status quo. Ports could include p5-DBD-mysql5 if they have a requirement for the new version (and add a restriction to only build with MySQL 8.x). While typing this out, trying to get some advice, I'm inclined to go for #2. But how can I go back a version? Bump PORTEPOCH? Sorry for the noise this caused. It wasn't intended. Greetings, Remko C. aka SirDice --000000000000767765061481f949 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All,

I took over maintainers= hip of p5-DBD-mysql last week. Apparently I unwittingly managed to poke a h= ornets nest. Upstream author changed the code to make it only compatible wi= th MySQL 8.x. I've tried patching out some of those changes but it requ= ires quite an effort and is, in the end, unmaintainable. So currently it is= broken if you change the default mysql to MariaDB.

At the moment I see a couple of options

1) = leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysql4 'legacy' versio= n port.
2) 'downgrade' p5-DBD-mysql to 4.051 and add= a p5-DBD-mysql5 'new' version port.

#1 wo= rks for the default MySQL (still at 8.0) but breaks if trying to build with= MariaDB. Arguments are made that those ports should switch to p5-DBD-maria= db instead. But this causes another set of problems, it's not a drop-in= replacement and some ports seem to have problems with DBD-MariaDB. Those p= orts could switch to the 'legacy' version until those issues are re= solved upstream. #1 also poses a problem if the default is switched to Mari= aDB and ports haven't been updated yet to depend on p5-DBD-mariadb or p= 5-DBD-mysql4.

#2 is probably the 'quickes= t' fix, it restores the status quo. Ports could include=20 p5-DBD-mysql5 if they have a requirement for the new version (and add a res= triction to only build with MySQL 8.x).

While= typing this out, trying to get some advice, I'm inclined to go for #2.= But how can I go back a version? Bump PORTEPOCH?

= Sorry for the noise this caused. It wasn't intended.=C2=A0
Greetings,

Remko C. aka SirDice

--000000000000767765061481f949--