Fix create-manifest.sh for raw pkg-message files to match porter's handbook.
AbandonedPublic
Actions

Authored by mandree on Apr 12 2020, 1:48 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Sun, Jul 12, 8:12 PM

	Unknown Object (File)
	Wed, Jul 8, 10:03 PM

	Unknown Object (File)
	Tue, Jul 7, 2:27 PM

	Unknown Object (File)
	Sat, Jul 4, 9:41 AM

	Unknown Object (File)
	Sat, Jul 4, 6:29 AM

	Unknown Object (File)
	Wed, Jul 1, 4:28 AM

	Unknown Object (File)
	Jun 4 2026, 7:24 AM

	Unknown Object (File)
	Jun 4 2026, 5:22 AM

View All Files

Subscribers

mat

Details

Reviewers

None

Group Reviewers

portmgr

Summary

The porter's handbook in section 9.1 (as of r54044) proudly proclaims

pkg-message supports two formats:

raw

A regular plain text file. Its message is always displayed, on install, and on upgrade.

But that's untrue. Fix create-manifest.sh so that freshly created packages live up to that standard.

Diff Detail

Repository

rP FreeBSD ports repository

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

mandree created this revision.Apr 12 2020, 1:48 PM

Herald added 1 blocking reviewer(s): portmgr. · View Herald TranscriptApr 12 2020, 1:48 PM

Herald added a subscriber: mat. · View Herald Transcript

I should mention that this was tested successfully on sysutils/e2fsprogs.

mandree mentioned this in rP531610: graphics/rawtherapee: avoid 2>&1 in test, UCL conversion of pkg-message.Apr 13 2020, 3:26 PM

In this case, the documentation is wrong, I will fix the documentation.

mandree abandoned this revision.May 9 2020, 6:17 PM

Revision Contents
Changeset List

Path

Size

Mk/

Scripts/

create-manifest.sh

2 lines

Diff 70450

View Options

Mk/Scripts/create-manifest.sh

Fix create-manifest.sh for raw pkg-message files to match porter's handbook.AbandonedPublicActions