Re: ctm(1) deprecation in the FreeBSD base system?

On Sun, Dec 23, 2018 at 12:27 AM Stefan Esser <se_at_freebsd.org> wrote:

> Am 23.12.18 um 02:39 schrieb Montgomery-Smith, Stephen:
> > On 12/21/18 10:03 PM, Julian H. Stacey wrote:
> >>> The port Makefile that I have prepared is attached below for reference.
> >>> Regards, STefan
> >>
> >> Thanks Stefan,
> >> I took current /usr/ports/misc/ctm/
> >> & converted Stephen's & my diffs to be automatic ports patches:
> >>
> http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/gen/misc/ctm/files/
> >>
> http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/gen/misc/ctm/README.JHS
> >>
> >> Stephens diffs are essential, without them CTM broke long ago,
> >> (5 digit numeric names maybe ?)
> >>
> >> I haven't checked all execution as my ctm_rmail scripts run
> >> automaticaly on an older release, not my current box, but this is
> >> running OK so far:
> >>      ctm -q /pub/FreeBSD/development/CTM/svn-cur/svn-cur.07000xEmpty.xz
> ;
> >>      ctm -q
> /pub/FreeBSD/development/CTM/svn-cur/svn-cur.07[0-9][0-9][0-9].xz
> >>
> >> Stephen may be best person to test delta builds, as hes the delta
> originator.
> >>
> >> Soonish I'll set up a
> >> [freebsd-]ctm-src-12 on http://mailman.berklix.org/mailman/listinfo
> >> if Stephens' & my requests to postmaster _at_ & mailman _at_ freebsd.org
> >> continues to get no response.
> >
> > Thank you for doing this, Stefan.  The additional patches mentioned by
> > Julian need to be included with the port before it can work and be
> > tested.  They are absolutely needed for the svn ctm deltas.
>
> Hi Stephen and Julian,
>
> I have converted the diffs into port patches (make makepatch) and
> updated the man-page revision dates of ctm.8 and ctm_rmail.8.
>
> The port update has been committed as r488168.
>
> I hope this brings the port to the level required to make the CTM
> port usable again.
>
> The patches could be imported to the Github repo (freebsd/ctm) after
> testing, but for now the patched port should suffice ...
>

I'd prefer that we do that, since git is a lot easier for managing change
that diffs in the tree, but I guess it isn't too urgent as the churn rate
here will be small.

Warner