9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: weigelt@metux.de,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Announce: standalone libixp
Date: Sat, 30 Jun 2007 18:47:44 +0200	[thread overview]
Message-ID: <5d375e920706300947g5313fe83i9b8a2144293091e@mail.gmail.com> (raw)
In-Reply-To: <20070630153814.GA17008@nibiru.local>

In case you didn't notice, there already exists a hg (mercurial)
repository for libixp: http://suckless.org/hg.rc/libixp

Most of your changes don't make any sense to me, pkg-config is at best
stupid, and shared libraries are plain disgraceful.

In any case there is a 9p-hackers
(http://groups.google.com/group/9p-hackers) list to discuss 9p
implementations and avoid filling 9fans with even more noise.

In any case, I will let kris answer it more detail, but if you have
any problem with the way libixp is packaged maybe you should have
contacted him first?

uriel

On 6/30/07, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
>
> I've just finished my standlone libixp package (forked from wmii).
>
> It's an completely standalone package with no deps (beside libc),
> provides pkg-config descriptor and shared library. Include files
> are installed in their own subdir ($INCLUDEDIR/9p-ixp).
>
> The problem with iounit=0 is fixed by setting it to a constant
> value (currently 512) in initfid() if its zero.
>
> An tiny testing client is also included (derived from wmiir).
>
>
> Available via CVS:
>
>     PServer:    nibiru.metux.de
>     Repository: 9p
>     Module:     libixp
>     Login:      anonymous/anonymous
>
> Feel free to test and use :)
>
>
> cu
> --
> ---------------------------------------------------------------------
>  Enrico Weigelt    ==   metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
>  Please visit the OpenSource QM Taskforce:
>         http://wiki.metux.de/public/OpenSource_QM_Taskforce
>  Patches / Fixes for a lot dozens of packages in dozens of versions:
>         http://patches.metux.de/
> ---------------------------------------------------------------------
>


  parent reply	other threads:[~2007-06-30 16:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 15:38 Enrico Weigelt
2007-06-30 16:47 ` Kris Maglione
2007-06-30 16:50   ` Kris Maglione
2007-06-30 17:30   ` Enrico Weigelt
2007-06-30 17:41     ` Kris Maglione
2007-07-01 12:50       ` Enrico Weigelt
2007-07-01 16:15         ` Iruata Souza
2007-07-01 10:11     ` Charles Forsyth
     [not found]     ` <dba1bd02516b1cfbf4119d7c567ec8e9@terzarima.net>
2007-07-01 12:42       ` Enrico Weigelt
2007-06-30 16:47 ` Uriel [this message]
2007-07-01 23:22   ` Roman Shaposhnik
2007-07-02  0:45     ` Enrico Weigelt
2007-07-03  3:50       ` Roman Shaposhnik
2007-07-03  4:09         ` Kris Maglione
2007-07-03 15:10         ` Enrico Weigelt
2007-07-03 19:45           ` Federico Benavento
2007-07-03 20:31           ` Jonathan Cast
2007-07-03 21:14             ` Wes Kussmaul
2007-07-03 21:51           ` Martin Neubauer
2007-07-03 23:16             ` Enrico Weigelt
2007-07-04  3:36               ` Iruata Souza

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=5d375e920706300947g5313fe83i9b8a2144293091e@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=weigelt@metux.de \
    /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.
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).