Hi!
> > Done.
>
> I noticed the port having several issues with portlint. If I start
> fixing them now, is there a way to release the port with identical ports
> version and patch level?
That depends on the changes. If the files ending up in the
stagedir are different, then the PORTREVISION++ ru
+--On 1 juillet 2016 14:23:53 +0200 Dirk Engling
wrote:
| On 25.06.16 16:45, Kurt Jaeger wrote:
|
|> Done.
|
| I noticed the port having several issues with portlint. If I start
| fixing them now, is there a way to release the port with identical ports
| version and patch level?
|
| I would not
On 25.06.16 16:45, Kurt Jaeger wrote:
> Done.
I noticed the port having several issues with portlint. If I start
fixing them now, is there a way to release the port with identical ports
version and patch level?
I would not want users bothering to install "new" versions that only
differ in the po
Hi!
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210223
>
> Any takers? It's been two weeks.
Done.
--
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210223
Any takers? It's been two weeks.
erdgeist
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsu