From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 4ED311381F1 for ; Mon, 22 Jan 2018 17:17:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5873E0965; Mon, 22 Jan 2018 17:17:42 +0000 (UTC) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4AA93E0953 for ; Mon, 22 Jan 2018 17:17:42 +0000 (UTC) Received: by mail-pf0-x232.google.com with SMTP id t5so7581661pfi.0 for ; Mon, 22 Jan 2018 09:17:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-transfer-encoding; bh=q+jELHrXygHgLCOOaoDXC2UTL+5KhCG0e2oggiNrL94=; b=h4NuGu2i6Mnsikxft6X61U/6wpgyJ7GIZGN30LfPIYTcZEGrTsOyjev4QFDJGTnOiz joFwc3ylmsMad1wgr9/3I5Jy0lZqlCokQiyIl+WcxNZNIYGrOductxyvzaEDTPOClXIZ 7FNeeOSYbXCoU2DeaQhgejbO58RKxMUptj0YvxBCPwfqIEHYjEZ0VthnLUSDfr1Fy7M5 OgyOBvjokDaVnnBorVOXiFIIuj4qfx6JX1e/repP9PbUlNHD64gTXxbG7uhBh6t/KBQQ 1HrXaSnFcZBvCdho6RXQu1IVN2nped0lQfALsb/7ToeyCzDgYKd3VnI68mNc3SS3nBH3 kXTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-transfer-encoding; bh=q+jELHrXygHgLCOOaoDXC2UTL+5KhCG0e2oggiNrL94=; b=fEwiCKGYfMa5r5s7cClbcLe9N7kKpOc/gKG6zS4AjI5aUZcv+fmMx8p8Pqs4r4UzNG AZfjyZDoej2sP/PBz2SMa7he3qGdfLeU3kqT3fpE9OVGGz+JtVWxyw2pXjb5CHBGCXuG NEcv5XQK7XMigLG1a+rS/yT6xa+uaxiLRi/w5a75uiCQXeLBRTWd4Ke9RaZ8YgPucl4Z TXZhrV0R6awvvgXSCHAUKqZi4lTZwiLMXrk0m9Wqv1iYl8Rg6IERohcdM9qlDBlTMJKg wat+smfgbJuD47mAzBB/GetEna19wk3vYHGK7JXuDhWdFaP+kV5RXtlj5J7DNollPebN fn+A== X-Gm-Message-State: AKwxytfdtvMtXSoSUnIHHX1SSdJ1xYdjckw8fyjBqIorKiLQzhsy+aw4 VLW0l8MrX+I8+o7YT1w+6WeIv885iof2HZt3AVo01Q== X-Google-Smtp-Source: AH8x2264TuMoB0qopu8DelEI6QmiwaK15FehvVLR0GMfDkYtcIvKbPjWOMW61ei6c1yUCJvcUXcIL+q2SXQk0nXwxr0= X-Received: by 10.99.120.66 with SMTP id t63mr7531197pgc.375.1516641460694; Mon, 22 Jan 2018 09:17:40 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Sender: freemanrich@gmail.com Received: by 10.100.134.1 with HTTP; Mon, 22 Jan 2018 09:17:40 -0800 (PST) In-Reply-To: <1516640255.1256.10.camel@gentoo.org> References: <1516640255.1256.10.camel@gentoo.org> From: Rich Freeman Date: Mon, 22 Jan 2018 12:17:40 -0500 X-Google-Sender-Auth: ypKZYk3YrAyWjbHx1kSHcJPhSGw Message-ID: Subject: Re: [gentoo-dev] version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass To: gentoo-dev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 090b92a1-ce44-4325-9fa5-eb4d09087454 X-Archives-Hash: eb3827c5dda8601a5ea2c302c0ddb5ec On Mon, Jan 22, 2018 at 11:57 AM, Micha=C5=82 G=C3=B3rny wrote: > W dniu nie, 21.01.2018 o godzinie 20=E2=88=B624=E2=80=89-0800, u=C5=BCytk= ownik Zac Medico > >> Should we tell users to use the emerge --changed-deps=3Dy option? Maybe >> make --changed-deps=3Dy a default setting? > > No. The idea is that not all dependency changes need to be explicitly > propagated. The developer needs to weigh the pros and cons > of propagating the change, and choose wisely. There is really no need to > enforce a lot of unnecessarily frequent rebuilds because of minor > dependency correction that doesn't really apply to the user. > I tend to agree, but one of the complications here is the break in time between the error and the consequences. If a dev commits a change and in six hours users start reporting breakage, then the error is easily identified and fixed, and the dev tends to learn not to do that again. If a dev commits a change, and in 12 months users get weird breakage when building or using other packages, then everybody runs around in circles, the error is at least somewhat painful to identify, and the dev has probably made the same error 5 other times since, if they're even still maintaining that package. A repoman warning would definitely help here. Forcing unnecessary rebuilds isn't really the ideal solution, though I'll admit I've been doing this for a while now since things were getting painful a while back. --=20 Rich