svn commit: r417672 - in head: . sysutils/rsyslog7 sysutils/rsyslog8 sysutils/rsyslog8/files

Matthew Seaman matthew at FreeBSD.org
Wed Jun 29 06:54:12 UTC 2016


On 28/06/2016 14:32, Brad Davis wrote:
> On Tue, Jun 28, 2016 at 11:30:15AM +0100, Matthew Seaman wrote:
>> On 06/27/16 18:04, Brad Davis wrote:
>>> Author: brd
>>> Date: Mon Jun 27 17:04:39 2016
>>> New Revision: 417672
>>> URL: https://svnweb.freebsd.org/changeset/ports/417672
>>>
>>> Log:
>>>   - Upgrade sysutils/rsyslog8 to 8.19.0 and make it the default
>>>   - Mark sysutils/rsyslog7 deprecated.
>>>   
>>>   Approved by:	bdrewery (mentor)
>>>
>>> Deleted:
>>>   head/sysutils/rsyslog8/files/patch-plugins__mmexternal__mmexternal.c
>>>   head/sysutils/rsyslog8/files/patch-plugins__omprog__omprog.c
>>>   head/sysutils/rsyslog8/files/patch-plugins_imfile_imfile.c
>>>   head/sysutils/rsyslog8/files/patch-runtime_stream.c
>>> Modified:
>>>   head/UPDATING
>>>   head/sysutils/rsyslog7/Makefile
>>>   head/sysutils/rsyslog8/Makefile
>>>   head/sysutils/rsyslog8/distinfo
>>
>> This has changed the package name from rsyslog8 to plain rsyslog, which
>> pkg(8) doesn't seem to be tracking properly.  IIRC, pkg uses MOVED to
>> track these sort of changes, but MOVED probably won't help here given it
>> only mentions port origins (which haven't changed.)
>>
>> Could you add to your note in UPDATING to tell pkg users that they will
>> need to manually 'pkg install rsyslog' to get the update?
> 
> Hmm, I would almost rather just remove rsyslog7 now and add the MOVED entry.
> 
> Thoughts?

I don't think that removing the rsyslog7 port would have any significant
effect here.  I'm talking about upgrading from rsyslog8-8.12.x to
rsyslog-8.19.0 via the use of binary packages -- it's all rsyslog-8.X.Y:
rsyslog-7 is not involved.

This actually highlights what is a missing bit of functionality in
pkg(8) -- knowing when a differently named package or packages are the
update path for an installed package.  It should be fairly easy to add a
'succeeds' field to the package meta-data -- the hard part will be
adding a mechanism to ports to record that data into the generated
packages, which probably means something like modifying the MOVED format
to add package names as well as port origins.

The rsyslog7-7.x.y case should be handled by MOVED entries: I don't
know, as I'm not using rsyslog7 anywhere and haven't tried.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20160629/1874a483/attachment.sig>


More information about the svn-ports-head mailing list