## Chris (portmas...@bsdforge.com):
> > but the way it currently interacts
> > with your port is not that fine: in the very least, it overwrites
> > your LICENSE variables, which cannot be your intention. (Try
> > "make -V LICENSE" in kde-icons-nuovoext2).
> Sorry. My bad. LGPL3 is now included
On 2021-05-14 14:19, Christoph Moench-Tegeder wrote:
## Chris (portmas...@bsdforge.com):
> but the way it currently interacts
> with your port is not that fine: in the very least, it overwrites
> your LICENSE variables, which cannot be your intention. (Try
> "make -V LICENSE" in
## Chris (portmas...@bsdforge.com):
> The problem I'm addressing in this case; is that the following as
> *always* worked for licenses which carried a copy in
> ${WRKSRC}/LICENSE_NAME:
The problem you're trying to address is only a consecutive error and
not the real problem.
As I wrote in my
On 2021-05-14 15:15, Christoph Moench-Tegeder wrote:
## Chris (portmas...@bsdforge.com):
The problem I'm addressing in this case; is that the following as
*always* worked for licenses which carried a copy in
${WRKSRC}/LICENSE_NAME:
The problem you're trying to address is only a consecutive
bob prohaska fbsd at www.zefox.net wrote on
Fri May 14 01:35:28 UTC 2021 :
> On Thu, May 13, 2021 at 01:35:50PM -0700, Mark Millard wrote:
> > You have apparently chosen to build/update ports via a
> > technique that requires you to manage the dependencies, at
> > least some of the time. (Not
On Fri, May 14, 2021 at 12:24:06PM +1000, Kubilay Kocak wrote:
>
> happy to help identify the root cause if you can jump on IRC
> (#freebsd-python @ freenode)
If sorting out the conflict between python versions helps the
community in general I'm willing to try. I simply use make in
the ports
