Re: Debian GNU/kFreeBSD

2011-02-13 Thread Mark Linimon
On Sun, Feb 13, 2011 at 10:12:05AM +0300, Odhiambo Washington wrote: > What is it that this Debian GNU/kFreeBSD ships in those 7 DVDs? Please ask that on one of their mailing lists; it's out of scope for the two mailing lists you posted to. mcl ___ free

Re: Re: Debian GNU/kFreeBSD

2011-02-13 Thread Maciej Milewski
Sunday 13 of February 2011 08:12:05 Odhiambo Washington napisał(a): > My question is: WHY need 7 DVDs??? DVDs?? Even M$ does not do such a crazy > thing with its bloat-ware!! FreeBSD ships 1 DVD. > What is it that this Debian GNU/kFreeBSD ships in those 7 DVDs? I think the answer for your first que

Re: Debian GNU/kFreeBSD

2011-02-13 Thread Chad Perrin
On Sun, Feb 13, 2011 at 10:12:05AM +0300, Odhiambo Washington wrote: > > My question is: WHY need 7 DVDs??? DVDs?? Even M$ does not do such a crazy > thing with its bloat-ware!! FreeBSD ships 1 DVD. > What is it that this Debian GNU/kFreeBSD ships in those 7 DVDs? It's probably just that portion o

Ports with duplicate LATEST_LINKS

2011-02-13 Thread Erwin Lansing
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports confli

Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Helmut Schneider
Hi, [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 [helmut@BSDHelmut ~]$ So, what's the difference between e.g. "LATEST_LINK=" and "LATEST_LINK?="? Thanks, Helmut ___

Re: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Chris Rees
On 13 February 2011 14:14, Helmut Schneider wrote: > Hi, > > [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? > /usr/ports/www/apache20/Makefile:LATEST_LINK=   apache20 > /usr/ports/www/apache22/Makefile:LATEST_LINK?=  apache22 > [helmut@BSDHelmut ~]$ > > So, what's the difference bet

Re: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Bob Eager
On Sun, 13 Feb 2011 14:14:17 + (UTC) "Helmut Schneider" wrote: > Hi, > > [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? > /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 > /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 > [helmut@BSDHelmut ~]$ > > So, what's

Re: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Helmut Schneider
Chris Rees wrote: > On 13 February 2011 14:14, Helmut Schneider wrote: > > [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? > > /usr/ports/www/apache20/Makefile:LATEST_LINK=   apache20 > > /usr/ports/www/apache22/Makefile:LATEST_LINK?=  apache22 > > [helmut@BSDHelmut ~]$ > > > > So,

Re: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Gary Jennejohn
On Sun, 13 Feb 2011 14:14:17 + (UTC) "Helmut Schneider" wrote: > [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? > /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 > /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 > [helmut@BSDHelmut ~]$ > > So, what's the diff

Re: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Eitan Adler
> > Is it up to the maintainer to decide which variables shall be > overwritable, or are there rules? > Generally one wants to respect as much of the user's wishes as they can. So things like CC, CFLAGS, CPP, CXX, etc should have a question mark. MAINTAINER and other internal port variable are gen

Re: Makefile, ${VARIABLE}= vs. ${VARIABLE}?=

2011-02-13 Thread Anonymous
Chris Rees writes: > On 13 February 2011 14:14, Helmut Schneider wrote: >> Hi, >> >> [helmut@BSDHelmut ~]$ grep -ir latest /usr/ports/www/apache2? >> /usr/ports/www/apache20/Makefile:LATEST_LINK= apache20 >> /usr/ports/www/apache22/Makefile:LATEST_LINK?= apache22 >> [helmut@BSDHelmut ~]$ >> >>

Re: Ports with duplicate LATEST_LINKS

2011-02-13 Thread Chris Rees
On 13 February 2011 13:00, Erwin Lansing wrote: > Dear port maintainers, > > The following list includes ports maintained by you that have duplicate > LATEST_LINK values.  They should either be modified to use a unique > LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting > each o

fixing the vulnerability in linux-f10-pango-1.22.3_1

2011-02-13 Thread Tom Uffner
is there any point in trying to update linux-f10-pango to address this vulnerability? Affected package: linux-f10-pango-1.22.3_1 Type of problem: pango -- integer overflow. Reference: I realize that I can install it w/ DI

Re: fixing the vulnerability in linux-f10-pango-1.22.3_1

2011-02-13 Thread Matthias Andree
Am 13.02.2011 22:53, schrieb Tom Uffner: > is there any point in trying to update linux-f10-pango to address this > vulnerability? > > Affected package: linux-f10-pango-1.22.3_1 > Type of problem: pango -- integer overflow. > Reference: >