Bug 72797

Summary: [NEW PORT] FreeBSD 5.3's /sbin/sha1
Product: Ports & Packages Reporter: Colin Percival <cperciva>
Component: Individual Port(s)Assignee: Ade Lovett <ade>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
sha1.shar none

Description Colin Percival 2004-10-17 22:10:22 UTC 
I want to use /sbin/sha1 in a port I'm writing, but it doesn't exist in
FreeBSD releases prior to 5.3.

Fix: Extract src/sbin/md5 from the FreeBSD 5.3 source tree, and turn it into
a port so that it can be installed on previous FreeBSDs.

(While there are other sha1 implementations in the ports tree, I'd
prefer to have this one added so that we can be certain of compatibility
with the sha1 in the base system.)

I hope I got the conditional IGNORE= ... part right.
How-To-Repeat: 
-bash-2.05b$ /sbin/sha1 foobar
-bash: /sbin/sha1: No such file or directory
Comment 1 clive 2004-10-19 06:59:40 UTC 
On Sun, Oct 17, 2004 at 09:05:02PM +0000, Colin Percival wrote:
> >Number:         72797
> >Category:       ports
> >Synopsis:       [NEW PORT] FreeBSD 5.3's /sbin/sha1

Hi,

    Providing utility for old releases via port is pretty cool, and
also benefits systems adminitered paranoids. <bikeshield>As to ports
paranoids, bsdsha1 shall be favored more.. like archivers/bsdtar.
</bikeshield>

> #	sysutils/sha1

-- 
Clive Tong-I Lin | http://tongi.org | PGP KeyID: A008C03E
Comment 2 colin.percival 2004-10-24 22:07:39 UTC 
I'm not really concerned about whether the port is called "sysutils/sha1" or 
"sysutils/bsdsha1", <bikeshed>although I think the former makes more sense, 
personally</bikeshed>.

Colin Percival
Comment 3 Ade Lovett freebsd_committer freebsd_triage 2004-10-25 19:36:17 UTC 
State Changed
From-To: open->closed

Committed, thanks!
Comment 4 Ade Lovett freebsd_committer freebsd_triage 2004-10-25 19:36:17 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ade

Finger of blame --> me :)