Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Aug 2006 09:21:23 +0400
From:      "Andrew Pantyukhin" <sat@FreeBSD.org>
To:        "Erwin Lansing" <erwin@FreeBSD.org>, ports-committers@freebsd.org,  cvs-ports@freebsd.org, cvs-all@freebsd.org
Subject:   Re: cvs commit: ports/devel Makefile ports/devel/p5-Linux-Pid Makefile distinfo pkg-descr pkg-plist
Message-ID:  <cb5206420608012221h388af866p829b254611bdb49d@mail.gmail.com>
In-Reply-To: <20060801214956.GB13326@droso.net>
References:  <200608012012.k71KCJba037198@repoman.freebsd.org> <20060801214956.GB13326@droso.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/2/06, Erwin Lansing <erwin@freebsd.org> wrote:
> On Tue, Aug 01, 2006 at 08:12:19PM +0000, Andrew Pantyukhin wrote:
> > sat         2006-08-01 20:12:19 UTC
> >
> >   FreeBSD ports repository
> >
> >   Modified files:
> >     devel                Makefile
> >   Added files:
> >     devel/p5-Linux-Pid   Makefile distinfo pkg-descr pkg-plist
> >   Log:
> >   Add port devel/p5-Linux-Pid:
> >
> >   Why should one use a module to get the PID and the PPID of a process
> >   where there are the $$ variable and the getppid() builtin? (Not
> >   mentioning the equivalent POSIX::getpid() and POSIX::getppid()
> >   functions.)
> >
> >   In fact, this is useful on Linux, with multithreaded programs. Linux'
> >   C library, using the linux thread model, returns different values of
> >   the PID and the PPID from different threads. (Other thread models such
> >   as NPTL don't have the same behaviour). This module forces perl to
> >   call the underlying C functions getpid() and getppid().
>
>
> So what does it do on FreeBSD? This looks pretty Linux specific.
>
> Not related to this specific commit, but the latest flurry of new perl
> modules has got me a bit worried. Are people actually using all these
> new modules or are they imported just because they are on CPAN? Coping
> with 15.000 ports is not easy and while I do not want to start imposing
> any rules (apart from the very liberal rules we already have) on new
> ports, we do need to judge the usefulness of every new port we add.

Linux here means "non-windows". I anticipated this kind of
questions but felt reluctant to change the portname just
because it was a linuxism, sorry.

I'm trying to port socialtext (http://www.asia.socialtext.net/stoss/)
It's a mammoth app, requiring dozens of p5 dependencies, and
some of them have yet to be added to the ports tree.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420608012221h388af866p829b254611bdb49d>