Date: Wed, 29 Mar 1995 04:44:57 -0800 From: asami@cs.berkeley.edu (Satoshi Asami/=?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: ports@FreeBSD.org Subject: Let's make the packages/ dir look clean! Message-ID: <199503291244.EAA04523@silvia.HIP.Berkeley.EDU>
next in thread | raw e-mail | index | archive | help
Hi ports folx. I have a suggestion about the packages (well I have
several but I'll discuss them one at a time to avoid bloating my mail :).
If you do a "ls" in ftp.freebsd.org's packages/ dir, you'll see a lot
of different kind of names...xdvi.tgz, mm2.7.tgz, jpeg-5a.tgz,
c-archie-1.4.1-FIXED.tgz, mule-2.2.2.tgz...it kinda gives a messy and
unorganized feeling. Since users will be looking into this directory
on the CDROM and the ftp site a lot, let's try to make it look neat! :)
My suggestion is that package names should be the format
<name>-<major>[.<minor>[.<patchlevel>]].tgz
Notes:
(1) Avoid periods (.) in <name> if possible (although I don't see any
packages with those kinds of names right now).
(2) The "-" after the <name> part is *mandatory*, I doesn't really
matter whether we have it or not as long as we standardize, but
since the majority of our ports already have it, I thought it's
better to push things that way.
(3) The version numbers (<major>, <minor> and <patchlevel>) are
integers or single alphabets or a combination of both. Avoid
things like "alpha" "fixed" unless absolutely necessary to
distinguish between two very similar ports. The last ".0" for
patchlevel 0 things can usually be omitted.
(4) This should be accomplished if people follow the (3) above, but
let's keep names short! I personally find it very annoying to do
a "ls" in that directory and see everything come out in one
column. I don't think the "-staticjpegtiff.tgz" sort of stuff are
really necessary (I love shared libs) but if we really have need
for them, maybe we can put them in a subdirectory "shared" or
something.
Since we already have "ghostscript-2.6.1.tgz" which we probably
don't want to shorten anymore without confusing users, let's make
that a yardstick for now. That's 21 characters, so if you have
something longer than this after following the rules (1)-(3)
above, tell me.
(5) The language specific ports (currently only Japanese) should have
"<language>-" ("jp-" for Japanese, etc.) attached in front of them
to avoid confusion with the originals. (Actually, this means when
I finally get the Japanese version of ghostscript, we'll have a
24-character port...I guess I'll call it "jp-gs-2.6.1.tgz" or
something....)
Note that the renaming of ports can be easily accomplished without
screwing up anything (thanks to Gary's modifications to bsd.port.mk)
by adding a PKGNAME variable definition in the Makefile.
I'd like people to take a look at their ports and decide on their new
names, since I don't really know how to chop up some of the numbers
(like, does "pfe099" mean "pfe-0.9.9" or "pfe-0.99" or "pfe-99" or...).
But if people don't do them within a week or so, I'll go in and change
them myself (unless somebody screams "foul", of course :).
What do you guys think?
Satoshi "the package janitor"
P.S. Examples of renaming:
xdvi.tgz -> xdvi-18.tgz, I suppose (patchlevel.h says "18")
mm2.7.tgz -> mm-2.7.tgz
jpeg-5a.tgz -> (no change, I guess)
c-archie-1.4.1-FIXED.tgz -> c-archie-1.4.1.tgz or archie-1.4.1.tgz
mule-2.2.2.tgz -> (no change)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503291244.EAA04523>