Prev: sysutils/pftop - parent terminal lost & CPU usage.
Next: INDEX build failed for 6.x
From: jhell on 19 Mar 2010 21:19

The above mentioned port installs or otherwise scatters quite a few (10 or
more) new directories into /usr/local/. Did I miss some configuration
setting that I had to explicitly state in order for everything to just be
installed in /usr/local/xorp or maybe in a more proper place.

Regards,

--

jhell

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Charlie Kester on 19 Mar 2010 21:38
On Fri 19 Mar 2010 at 18:19:53 PDT jhell wrote:
>
>The above mentioned port installs or otherwise scatters quite a few
>(10 or more) new directories into /usr/local/. Did I miss some
>configuration setting that I had to explicitly state in order for
>everything to just be installed in /usr/local/xorp or maybe in a more
>proper place.

Looking at the pkg-plist for the port, this is the normal, expected
installation. I don't see many lines controlled by a PLIST_SUB, so I
don't think this can be changed by setting some options.
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Bruce Simpson on 19 Mar 2010 22:15
On 03/20/10 01:19, jhell wrote:
>
> The above mentioned port installs or otherwise scatters quite a few
> (10 or more) new directories into /usr/local/. Did I miss some
> configuration setting that I had to explicitly state in order for
> everything to just be installed in /usr/local/xorp or maybe in a more
> proper place.

XORP as of 1.7-WIP in SVN is now compliant with the Filesystem Hierarchy
Standard.

Its directory is thus more in line with other packages for free
UNIX-like operating systems.

I appreciate your feedback that this may have violated POLA for you,
however, it's pretty much a prerequisite for getting it shipped in
Ubuntu and other UNIX-like systems.

If you have any further queries please direct them to the xorp-users and
xorp-hackers mailing lists.

Thank you for your interest in XORP.

regards,
BMS
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Bruce Simpson on 19 Mar 2010 22:30
P.S. there is a pkg-message for the legacy net/xorp package which
explains why XORP needs PREFIX to be set to other than the default. If
this is a problem for you consider net/xorp-devel
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: jhell on 20 Mar 2010 07:35

On Fri, 19 Mar 2010 22:30, Bruce Simpson wrote:
In Message-Id: <4BA4334F.3010405(a)incunabulum.net>

> P.S. there is a pkg-message for the legacy net/xorp package which explains
> why XORP needs PREFIX to be set to other than the default. If this is a
> problem for you consider net/xorp-devel
>

Hey! Thanks.

I didn't have that much time to look at it originally and I usually try to
stick to non-devel based distributions but I think in the case of this
software I will end up making an exception.

Problem lays between a overnight away from desk install and coming back a
week later to configure it.

Thanks for pointing this out.

--

jhell

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 | 
Pages: 1
Prev: sysutils/pftop - parent terminal lost & CPU usage.
Next: INDEX build failed for 6.x