Dovecot packages

[Doug Hardie]

Correct. There is no port tree. Packages are used exclusively 

> On May 23, 2019, at 01:16, @lbutlr <kremels at kreme.com> wrote:
> 
>> On 22 May 2019, at 16:41, Doug Hardie <bc979 at lafn.org> wrote:
>> It appears that the dovecot package is now the one that is maintained and dovecot2 package has remained stagnant.  
> 
> You didn't replace your port tree when you upgraded to 12.0-RELEASE.
> 
> I think that portsnap fetch extract ensures your ports tree matches the current ports.
> 
> Ah, yes, from the man -8 portsnap:
> 
>     extract      Extract a ports tree, replacing existing files and
>                  directories.  NOTE: This will remove anything occupying the
>                  location where files or directories are being extracted; in
>                  particular, any changes made locally to the ports tree (for
>                  example, adding new patches) will be silently obliterated.
> 
> ===>
>                  Only run this command to initialize your portsnap-maintained
>                  ports tree for the first time, if you wish to start over
>                  with a clean, completely unmodified tree, or if you wish to
>                  extract a specific part of the tree (using the path option).
> ===>
> 
> -- 
> Whoever had created humanity had left in a major design flaw. It was its
> tendency to bend at the knees. --Feet of Clay
> 
> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"