Bug 46781 - shells/scponly - pkg-plist incorrect
Summary: shells/scponly - pkg-plist incorrect
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-05 13:10 UTC by Philip Paeps
Modified: 2003-01-05 18:30 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Paeps 2003-01-05 13:10:02 UTC 
	
	After the update to scponly 3.4, I noticed that the binary moved from
	${LOCALBASE}/sbin to ${LOCALBASE}/bin.  I don't mind that change (well, I
	did, as some users couldn't log in because their shell was set to sbin),
	but the pkg-plist still says sbin, whilst the port installs in bin.

Fix: 

There're two ways to fix this.  The one I prefer is just to change the
	pkg-plist to say 'bin' instead of 'sbin'.  I think the shell is 'better'
	placed in bin than sbin, as other shells (also those in the base-system)
	also live in bin.

	The second approach would be to modify the port's Makefile.in to pop the
	binary into sbin instead of bin.  This would have as advantage that people
	upgrading wouldn't find users locked out...

	Dilemma :-)
How-To-Repeat: 	
	Install shells/scponly.  The port will install in ${LOCALBASE}/bin.  When
	using portupgrade to upgrade a previous version, the old version in sbin
	will vanish, and the new version will appear in bin.
Comment 1 Ying-Chieh Liao freebsd_committer freebsd_triage 2003-01-05 18:30:33 UTC 
State Changed
From-To: open->closed

committed, thanks