zsh-users
 help / color / mirror / code / Atom feed
From: James Devenish <j-devenish@users.sourceforge.net>
To: zsh-users@sunsite.dk
Subject: Re: Proposed changes to _bsd_pkg -- request for comments
Date: Fri, 3 Jan 2003 18:30:01 +0800	[thread overview]
Message-ID: <20030103103001.GA19326@gulag.guild.uwa.edu.au> (raw)
In-Reply-To: <20030103111950.A31382@globnix.org>

In message <20030103111950.A31382@globnix.org>
on Fri, Jan 03, 2003 at 11:19:50AM +0100, Phil Pennock wrote:
> It's also worth noting that all the *BSDs have online man-pages.

LOL pretty stupid of me to overlook that. I could have looked at the
FreeBSD man pages long ago! Oh well.

> OpenBSD:

No worries, I have machines running OpenBSD (but not {Free,Net}BSD).

> Under FreeBSD, packages are strictly optional and are built from the
> installed files (as opposed to the OpenBSD fake-root install, then
> package creation, then real install from packages).  _If_
> /usr/ports/packages has been created, then packages will be created
> under there; if not, then they'll be created inside the ports directory
> and you'll have things like /usr/ports/shells/zsh/zsh-4.0.6.tgz.

Interesting. Though _bsd_pkg was made for FreeBSD originally, I wonder
if it is still accurate for FreeBSD.

> Also, FreeBSD is moving steadily towards bzip2 instead of gzip, so
> you'll see packages with .tbz2 extensions (or, for a short while, there
> were .tbz extensions, still for bzip2).  Which will be created, .tbz2 or
> .tgz, depends simply upon how old your ports infrastructure makefiles
> are.  My workstation has both, simply because I keep my ports tree
> updated, including /usr/ports/Mk/.

Okay, I introduced a switch statement for filename extensions because it
seemed to be more involved than simply t[gbz]. I should probably dig up
archives of the -workers thread on that topic, to see if there is
anything about what you just mentioned.

> -Phil (the person to blame if you dislike OpenBSD's not including zftp
>        unless you explicitly pick that flavo(u)r of zsh.)

:)



      reply	other threads:[~2003-01-03 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 14:04 Refactoring _bsd_pkg James Devenish
2003-01-02 14:41 ` Oliver Kiddle
2003-01-02 15:37   ` James Devenish
2003-01-03  8:39 ` Proposed changes to _bsd_pkg -- request for comments James Devenish
2003-01-03  9:14   ` Roman Neuhauser
2003-01-03 10:19   ` Phil Pennock
2003-01-03 10:30     ` James Devenish [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030103103001.GA19326@gulag.guild.uwa.edu.au \
    --to=j-devenish@users.sourceforge.net \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).