From owner-freebsd-doc Wed Feb 13 19:28:39 2002 Delivered-To: freebsd-doc@freebsd.org Received: from wrath.forked.net (wrath.forked.net [216.65.131.190]) by hub.freebsd.org (Postfix) with ESMTP id 12BC037B417; Wed, 13 Feb 2002 19:28:32 -0800 (PST) Received: from wrath.forked.net (IDENT:logo@localhost [127.0.0.1]) by wrath.forked.net (8.12.2/8.12.2) with ESMTP id g1E3SQUH010627; Wed, 13 Feb 2002 19:28:26 -0800 Received: from localhost (logo@localhost) by wrath.forked.net (8.12.2/8.12.2/Submit) with ESMTP id g1E3SQYU010624; Wed, 13 Feb 2002 19:28:26 -0800 X-Authentication-Warning: wrath.forked.net: logo owned process doing -bs Date: Wed, 13 Feb 2002 19:28:26 -0800 (PST) From: Valentino Vaschetto X-X-Sender: logo@wrath.forked.net To: Nik Clayton Cc: Dima Dorfman , Subject: Re: replacement In-Reply-To: <20020213230809.I92878@canyon.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > 1. Definitely 'package', not 'port'. Ports are just the infrastructure > that produce packages. Why package? We didnt use before in our sgml documents, so I think that we should keep it as "port". In html format, when a user clicks on the link for net/cvsup for example, it takes them to the cvsup port's page, and from there they have the option to download the package. When a user clicks on the link, it doesn't go and start downloading that package. Am I wrong? If I am, just ignore me on this comment. > 2. I have a nagging feeling that we should make sure the package's > category is included somewhere that DSSSL/XSLT stylesheets can > access it. > > net/cvsup > > is less easy to parse (in a stylesheet) than something like > > cvsup I agree with this. Even though it is extra typing, you're right that it would be easier to introduce into our stylesheet. > We can always make these entities, something like > > &pkg.net.cvsup; Deadly. If we did it this way, would'nt we have to add new entities every time we get a new port? Even though it's easier than using the tag, I think that it would be a hassle to keep up to date with all the new ports. -val To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message