Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!inferno.mpx.com.au!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!uuneo.neosoft.com!news
From: conrads@neosoft.com (Conrad Sabatier)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: What a lovely dream I had last night!
Date: 27 Dec 1996 13:28:00 GMT
Organization: NeoSoft, Inc.
Lines: 40
Message-ID: <5a0it0$9bc@uuneo.neosoft.com>
References: <59mgl3$lus@uuneo.neosoft.com> <59n2qf$790@uriah.heep.sax.de>
<59prf3$foi@uuneo.neosoft.com> <59um1h$nr6@uriah.heep.sax.de>
NNTP-Posting-Host: 206.27.165.136
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33346
In article <59um1h$nr6@uriah.heep.sax.de>,
j@uriah.heep.sax.de (J Wunsch) writes:
> conrads@neosoft.com (Conrad Sabatier) wrote:
>
>> I'm pleased to report I have done just that! My very first "official"
>> port (xless). Submitted it yesterday.
>
> Hmm, haven't you withdrawn it meanwhile? At least, that's how it
> sounded.
Well, yes and no. I did send mail to freebsd-ports asking them to remove
it, as I had made some minor mistakes, but I immediately resubmitted the
corrected version.
> Btw., it would be better to use send-pr to submit a port. This way it
> won't fall through the cracks.
Hmmm. No mention of this in the handbook (at least not that I saw). I
tried very carefully to follow the prescribed protocol as outlined there.
It says to upload to /pub/FreeBSD/incoming and then send mail to
freebsd-ports@freebsd.org.
By the way, there are a few details that get glossed over in the handbook.
For instance, on creating the actual port tarball. What file ownerships/
permissions to use, should a port create its own directory, or let the
user decide where he wants to unpack it, that sort of thing.
Minor oversights, but important ones, nonetheless. Overall, though, I
found the section on porting quite well written and very helpful. What I
would *really* like to see added is a more detailed discussion of
bsd.port.mk and its various options.
Granted, one *could* examine existing ports for examples, but this should
not be necessary with more complete docs.
--
Conrad Sabatier |
conrads@neosoft.com | Eschew obfuscation.
http://www.neosoft.com/~conrads |