Date: Wed, 13 Aug 2014 09:05:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192633] New: port-mgmt/portlint: Feature request to check for muted installation commands Message-ID: <bug-192633-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192633 Bug ID: 192633 Summary: port-mgmt/portlint: Feature request to check for muted installation commands Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: marino@FreeBSD.org A common mistake found in do-install and post-install targets is the muting= of installation commands. It's permissible to mute mkdir commands, but not install commands. This is a request to have portlint check for this proble= m if it can. excerpt of conversation on port-committers@ +--On 13 ao=C3=BBt 2014 10:49:56 +0200 John Marino <freebsd.contact@marino.= st> wrote: | On 8/13/2014 10:40, Mathieu Arnold wrote: |> +--On 13 ao=C3=BBt 2014 10:16:34 +0200 Thomas Zander <riggs@freebsd.org> |> wrote: |> | On 13 August 2014 10:04, Alexey Dokuchaev <danfe@freebsd.org> wrote: |> |> On Wed, Aug 13, 2014 at 08:06:06AM +0200, John Marino wrote: |> |>> It's been said, or at I how I interpreted it, that policy has already |> |>> been established as a result of a long discussion. And that the |> |>> outcome is: 1) You can't mute installation commands |> |>> 2) You may mute mkdir commands at your preference (with an implied |> |>> it's more popular to mute mkdir than not) |> |>=20 |> |> Correct. It's been a long tradition within the ports to do it this |> |> way, |> |=20 |> | If that is our convention, then why not clearly defining the rules in |> | the porter's handbook? |> | (At least I could not find these conventions in it in a quick search.) |> | We can hardly expect new contributors to know this if it's not in the |> | docs. |>=20 |> I thought I wrote a bit about that, I discovered this morning that my |> memory is not what it used to be, I'm doing that now. |=20 | Is this policy something portlint is technically capable of checking? | if so, I don't mind opening a feature request PR for portlint to do it. | John I have no idea of how portlint works, so I can't comment on that, but it would be nice if it could check that. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192633-13>