On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote:
> > > It also doesn't work if someone runs make rmconfig, or make config again
> > > and changes things after the port is installed.
> > >
> > > It probably doesn't work if a package was used to install either.
> >
> > Create a slave por
On Friday 21 December 2007 07:50:59 pm Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 04:13:46PM -0600, Josh Paetzel wrote:
> > On Friday 21 December 2007 03:43:19 pm Edwin Groothuis wrote:
> > > On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > > > I've recently run across some b
On Fri, Dec 21, 2007 at 04:13:46PM -0600, Josh Paetzel wrote:
> On Friday 21 December 2007 03:43:19 pm Edwin Groothuis wrote:
> > On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > > I've recently run across some brokeness in ports that would be relatively
> > > trivial to deal with
On Saturday 22 December 2007 01:29:23 Pav Lucistnik wrote:
> Danny Pansters píše v so 22. 12. 2007 v 00:07 +0100:
> > How about e.g. LIB_DEPENDS=artsdsp:/usr/portss/[EMAIL PROTECTED] to
> > squash two
> > flies at once.
> >
> > The idea being that if the port is not installed it yet, it could be
>
> I bet most/many non-default ports don't get properly packaged anyway as
> it is.
I meant: ports with non-default OPTIONS. Sorry.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send a
--On December 22, 2007 12:07:45 AM +0100 Danny Pansters <[EMAIL PROTECTED]>
wrote:
I like the idea to do something with options. Optionifying ports is all
nice and well, but to make it meaningful, ports should be able to know
about each other's options. I actually have been working a bit on a
Danny Pansters píše v so 22. 12. 2007 v 00:07 +0100:
> How about e.g. LIB_DEPENDS=artsdsp:/usr/portss/[EMAIL PROTECTED] to
> squash two
> flies at once.
>
> The idea being that if the port is not installed it yet, it could be built
> with make WITHOUT_NAS=1 automagically. Something like this is
On Friday 21 December 2007 22:43:19 Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > I've recently run across some brokeness in ports that would be relatively
> > trivial to deal with if one port had a way to know about the OPTIONS
> > another port was comp
On Friday 21 December 2007 03:43:19 pm Edwin Groothuis wrote:
> On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> > I've recently run across some brokeness in ports that would be relatively
> > trivial to deal with if one port had a way to know about the OPTIONS
> > another port was c
On Fri, Dec 21, 2007 at 03:24:20PM -0600, Josh Paetzel wrote:
> I've recently run across some brokeness in ports that would be relatively
> trivial to deal with if one port had a way to know about the OPTIONS another
> port was compiled with.
I have been working on it a not-so-long-time-ago and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edwin Groothuis wrote:
> On Thu, Dec 20, 2007 at 08:36:32PM -0500, Chuck Robey wrote:
>> Back last time I was last active,Satoshi Asami was the "Portsmeister". I
>> dunno if that term is used anymore, but I need to find out if one person is
>> in
>>
I've recently run across some brokeness in ports that would be relatively
trivial to deal with if one port had a way to know about the OPTIONS another
port was compiled with.
My initial thought was to register the state of OPTIONS in to /var/db/pkg.
This solves all of the problems that I know
On Fri, Dec 21, 2007 at 10:42:50PM +0300, Max Brazhnikov wrote:
> I've submitted several pr (ports/117807, ports/118269, ports/118502) to
> fix/update ports which are maintained by @freebsd.org people.
Of these, the last 2 came in during the time that the ports tree was
frozen in preparation for
Hi,
I've submitted several pr (ports/117807, ports/118269, ports/118502) to
fix/update ports which are maintained by @freebsd.org people. But I still
have no answer from them, also seems that the last port (multimedia/kplayer)
is abandoned. Is there a way to resolve the situation?
Max
Yuri Pankov wrote:
On Fri, Dec 21, 2007 at 11:50:15AM +0200, Rodion Turlac wrote:
There seems to be a problem with Makefile - it should include
bsd.port.pre.mk before testing variables set by OPTIONS. Try attached
patch. Maintainer Cc'ed.
I tried it, all is fine. Thanks
--
Rodion Turlac
On Fri, Dec 21, 2007 at 11:50:15AM +0200, Rodion Turlac wrote:
> Hi!
> Havp port is not built with clamav support
>
> mail# cat /var/db/ports/havp/options
> # This file is auto-generated by 'make config'.
> # No user-servicable parts inside!
> # Options for havp-0.85
> _OPTIONS_READ=havp-0.85
> WIT
Hi!
Havp port is not built with clamav support
mail# cat /var/db/ports/havp/options
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
# Options for havp-0.85
_OPTIONS_READ=havp-0.85
WITHOUT_SSL=true
WITH_CLAMAV=true
WITHOUT_TROPHIE=true
cd /usr/ports/www/havp/
ma
Hi,
I looked in the ports database and saw your arm-elf-gcc port. The
version is very old and therefore I decided to build it myself. Perhaps
it is an idea to update the port to use gcc version 4.2 ?
Best regards,
Ewout Boks
___
freebsd-ports@freebsd.o
18 matches
Mail list logo
