zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: James Devenish <j-devenish@users.sourceforge.net>
Cc: zsh-users@sunsite.dk, David Lebel <lebel@openbsd.org>
Subject: Re: Refactoring _bsd_pkg
Date: Thu, 02 Jan 2003 15:41:52 +0100	[thread overview]
Message-ID: <2419.1041518512@finches.logica.co.uk> (raw)
In-Reply-To: <20030102140412.GG2863@gulag.guild.uwa.edu.au>

On 2 Jan, you wrote:
> 
> The platform for which _bsd_pkg is relevant to me is OpenBSD.  Until
> today, I hadn't realised that _bsd_pkg even existed.  Having just tried
> it, I think the reason I didn't notice is that it behave{s,d} incorrectly
> and therefore I didn't realised that something intelligent was at work.

It was written originally for FreeBSD with some NetBSD options being added
later. You're the first person I remember mentioning its use with OpenBSD.
Though doubtless there are people who have tried it and just ignored the
incorrect behaviour.

> Also, I notice that the OpenBSD ports tree contains a patch that I can't
> see in zsh CVS HEAD. I have attached the completion function that I have
> been using for pkg_delete and pkg_info. Mine is concise, partly because
> it does not support pkg_add, pkg_create, or other BSDs. However, there
> are some salient differences. Having downloaded the _bsd_pkg HEAD, it
> appears that there are some errors in it from the OpenBSD perspective
> (as in previous versions). I don't know whether this is because other
> BSDs are different or because no one has noticed.

Is there any chance that you could merge your OpenBSD functions into
the _bsd_pkg HEAD and then submit a patch to the zsh-workers list. They
can then be committed to cvs without upsetting FreeBSD users. It should
just be a matter of sticking an `openbsd*)' section in the various `case
"$OSTYPE" in' parts of the function. If not, I can attempt to do it
but I'll probably make a mess of it as I don't have access to any BSD
systems to check it against.

Cheers

Oliver

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.


  reply	other threads:[~2003-01-02 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 14:04 James Devenish
2003-01-02 14:41 ` Oliver Kiddle [this message]
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

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=2419.1041518512@finches.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=j-devenish@users.sourceforge.net \
    --cc=lebel@openbsd.org \
    --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).