On 08/29/2011 23:25, Mark Linimon wrote:
> So, the right answer may be "it depends".
I think my point is, it shouldn't. If a port is important/popular than
it will be quickly fixed. If not, it goes away. Everyone wins.
--
Nothin' ever doesn't change, but nothin' changes much.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/30/11 01:17, Doug Barton wrote:
> On 08/29/2011 23:25, Mark Linimon wrote:
>> So, the right answer may be "it depends".
>
> I think my point is, it shouldn't. If a port is important/popular
> than it will be quickly fixed. If not, it goes away
Chad Perrin wrote:
>Of course, your goal is apparently to
>convince me that yours are the "correct" priorities.
Indeed i think having the correct priorities is essential when choosing
between different options, and i am sincerely convinced that my choices
are shared by a lot more people than your
Doug Barton wrote:
> I'm doing some updates and came across mail/postfix-policyd-spf which
> relies on mail/libspf2-10. The latter had a vuxml entry added on
> 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to
> remain in the tree vulnerable for almost 3 years?
>
> Wouldn't
On 30 Aug 2011 10:15, "Michel Talon" wrote:
>
> Chad Perrin wrote:
>
> >Of course, your goal is apparently to
> >convince me that yours are the "correct" priorities.
>
> Indeed i think having the correct priorities is essential when choosing
> between different options, and i am sincerely convince
On 2011-Aug-29 13:45:34 +0400, Ruslan Mahmatkhanov wrote:
>Peter Jeremy wrote on 29.08.2011 07:29:
>> Turns out that my python was dodgy.
...
>And did you realize what python option had triggered that? I'm curious
>since i'm wasn't able to reproduce it here. For me it looks like
>upstream bug de
Am 28.08.2011 22:42, schrieb Doug Barton:
> On 8/28/2011 10:46 AM, Sahil Tandon wrote:
>> On Sun, 2011-08-28 at 19:41:02 +0200, Matthias Andree wrote:
>>
>>> just a brain flash: bsd.port.mk currently re-prompts OPTIONS if
>>> they've changed, for instance, through addition.
>>>
>>> Should we change
On Tue, Aug 30, 2011 at 11:13:58AM +0200, Michel Talon wrote:
> i went to a store to buy a new laptop, i went with two CDROMs, an Ubuntu
> one and a FreeBSD one. Guess which of the two supported the network
> controllers in the laptops i tried?
And guess which of them ran binary blobs.
__
On 24/08/2011 12:13, Baptiste Daroussin wrote:
libreoffice as openoffice are difficult ports to maintain, to not
hesitate to join the office@ team to help, test, discuss about the
office related task.
Not volunteering but just wanted to thank you - I really couldn't use
FreeBSD on any desktop
On Mon, Aug 29, 2011 at 11:40:25AM +0200, Matthias Andree wrote:
> Euhm, while workable I don't like that approach. And I conclude that
> the way the OPTIONS system currently works has a serious shortcoming, in
> that it does not report changed defaults to the user.
>
> Basically in this situatio
Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh:
> sunpoet 2011-08-30 08:23:18 UTC
>
> FreeBSD ports repository
>
> Modified files:
> mail/procmailMakefile
> Log:
> - Take maintainership
>
> Revision ChangesPath
> 1.60 +1 -1 ports/mail/procmail/M
Am 30.08.2011 12:28, schrieb Frank Wall:
> On Mon, Aug 29, 2011 at 11:40:25AM +0200, Matthias Andree wrote:
>> Euhm, while workable I don't like that approach. And I conclude that
>> the way the OPTIONS system currently works has a serious shortcoming, in
>> that it does not report changed default
Hi!
> > Modified files:
> > mail/procmailMakefile
[...]
> Now that you're maintaining it I seek you to please let this
> unmaintained unclean code from our FreeBSD ports world and deprecate it.
[...]
> maildrop (courier's filtering agent) has been around for nearly as long
> and wor
Matthias Andree wrote on 30.08.2011 15:06:
Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh:
sunpoet 2011-08-30 08:23:18 UTC
FreeBSD ports repository
Modified files:
mail/procmailMakefile
Log:
- Take maintainership
Revision ChangesPath
1.60 +1 -
Am 30.08.2011 13:11, schrieb Kurt Jaeger:
> Hi!
>
>>> Modified files:
>>> mail/procmailMakefile
> [...]
>> Now that you're maintaining it I seek you to please let this
>> unmaintained unclean code from our FreeBSD ports world and deprecate it.
> [...]
>> maildrop (courier's filterin
On Tue, Aug 30, 2011 at 01:11:52PM +0200, Kurt Jaeger wrote:
> - Can it use the 700+ lines long .procmailrc I have running
> in a criticial application or do I have to migrate that ?
I would suggest to migrate to something new. While searching
for a procmail replacement myself, I've even found
[maildrop]
> > - Can it use the 700+ lines long .procmailrc I have running
> > in a criticial application or do I have to migrate that ?
>
> You'd have to migrate that.
That's what I assumed.
> Bottom line: the sooner we get rid from procmail the better.
There are many other applications that
Matthias Andree writes:
> > The user decided to go a specific path by initially choosing a
> > specific set of OPTIONs. We *must* assume that the user had good
> > reasons to do so. We should *not* assume the user has no idea what
> > he's doing and needs to be guided. The latter would make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
I have a question about a commit you made in February 2011:
http://www.freshports.org/commit.php?message_id=201102250750.p1p7ofdg016...@repoman.freebsd.org&files=yes
Part of the commit changed:
USE_PYTHON= 2.4+
to
USE_PYTHON= 2.
Greg Larkin wrote on 30.08.2011 17:05:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
I have a question about a commit you made in February 2011:
http://www.freshports.org/commit.php?message_id=201102250750.p1p7ofdg016...@repoman.freebsd.org&files=yes
Part of the commit changed:
USE
Hi,
I'd like to take maintainership of following unmaintained now ports:
mail/popper
mail/miltergreylist
mail/milter-greylist-devel
mail/premail
--
Mikhail
m.tsatse...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote:
> Greg Larkin wrote on 30.08.2011 17:05:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi Martin,
>>
>> I have a question about a commit you made in February 2011:
>> http://www.freshports.org/
Greg Larkin wrote on 30.08.2011 17:56:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote:
Greg Larkin wrote on 30.08.2011 17:05:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
I have a question about a commit you made in February 2011:
http
On Tue, 30 Aug 2011, Matthias Andree wrote:
Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh:
sunpoet 2011-08-30 08:23:18 UTC
FreeBSD ports repository
Modified files:
mail/procmailMakefile
Log:
- Take maintainership
Revision ChangesPath
1.60 +1 -1
Matthias Andree wrote:
> Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh:
> > sunpoet 2011-08-30 08:23:18 UTC
> >
> > FreeBSD ports repository
> >
> > Modified files:
> > mail/procmailMakefile
> > Log:
> > - Take maintainership
> >
> > Revision ChangesPath
>
On Tue, Aug 30, 2011 at 11:13:58AM +0200, Michel Talon wrote:
> Chad Perrin wrote:
> >
> >Of course, your goal is apparently to
> >convince me that yours are the "correct" priorities.
>
> Indeed i think having the correct priorities is essential when choosing
> between different options, and i am
On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote:
> I'm doing some updates and came across mail/postfix-policyd-spf which
> relies on mail/libspf2-10. The latter had a vuxml entry added on
> 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to
> remain in the tree vulne
Am 30.08.2011 15:04, schrieb Mikhail Tsatsenko:
> I'd like to take maintainership of following unmaintained now ports:
> mail/popper
> mail/miltergreylist
> mail/milter-greylist-devel
> mail/premail
Hi Mikhail,
thanks for volunteering!
You are now the maintainer of these four ports (actually th
Am 30.08.2011 14:27, schrieb Kurt Jaeger:
> [maildrop]
>>> - Can it use the 700+ lines long .procmailrc I have running
>>> in a criticial application or do I have to migrate that ?
>>
>> You'd have to migrate that.
>
> That's what I assumed.
>
>> Bottom line: the sooner we get rid from procmail
On the procmail depracation topic, Warren Block wrote:
> Some initial searching shows that maildrop is a functional replacement
> and can be used with sendmail's local_procmail feature, but the rules
> are different. There could be other functionality which users depend
> on, like formail, which
Am 30.08.2011 17:24, schrieb Julian H. Stacey:
> Matthias Andree wrote:
>> Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh:
>>> sunpoet 2011-08-30 08:23:18 UTC
>>>
>>> FreeBSD ports repository
>>>
>>> Modified files:
>>> mail/procmailMakefile
>>> Log:
>>> - Take maintai
> ... the US
> patent system has become horribly broken in practice. The world's
> biggest patent-holders that actually produce anything pretty much all
> agree that the system is horribly broken, and mostly collect patents for
> defensive use.
Not just USA but Europe too, etc.
A European Pat
Could we please change the Subject line to match the content now?
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Quoth Matthias Andree on Tuesday, 30 August 2011:
> Am 30.08.2011 14:27, schrieb Kurt Jaeger:
> > [maildrop]
> >>> - Can it use the 700+ lines long .procmailrc I have running
> >>> in a criticial application or do I have to migrate that ?
> >>
> >> You'd have to migrate that.
> >
> > That's what
On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote:
> How about if we added a new tag "OBSOLESCENT" or so that permits
> building the software only if it's already installed but refuses new
> installations?
Right now if you set DEPRECATED you'll get a warning. Shouldn't
that be suffi
Hi,
I noticed a problem with rc script for openvpn-2.2.1 on recent FreeBSD
8-STABLE (Aug 13 20:33:31 CEST 2011).
It failed to restart if I have the following in rc.conf
openvpn_bp_office_if="tap bridge"
# service openvpn_bp_office restart
Stopping openvpn_bp_office.
Waiting for PIDS: 75580.
Am 30.08.2011 18:40, schrieb Miroslav Lachman:
> Hi,
>
> I noticed a problem with rc script for openvpn-2.2.1 on recent FreeBSD
> 8-STABLE (Aug 13 20:33:31 CEST 2011).
> It failed to restart if I have the following in rc.conf
>
> openvpn_bp_office_if="tap bridge"
>
>
> # service openvpn_bp_offi
On 30 August 2011 17:39, Mark Linimon wrote:
> On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote:
>> How about if we added a new tag "OBSOLESCENT" or so that permits
>> building the software only if it's already installed but refuses new
>> installations?
>
> Right now if you set DEP
When updating firefox to the latest version (from ports) it complained
about hg not being found. Apparently a dependency to mercurial is
missing. I haven't checked why, installing it resolved it.
Can you please show us exact error message for further investigation?
Turns out this is an (alm
Am 30.08.2011 19:29, schrieb Chris Rees:
> On 30 August 2011 17:39, Mark Linimon wrote:
>> On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote:
>>> How about if we added a new tag "OBSOLESCENT" or so that permits
>>> building the software only if it's already installed but refuses new
On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote:
> It only warns, it does not prevent fresh installs on systems that don't
> have the same port/package already installed.
"code, not policy" ... ?
mcl
___
freebsd-ports@freebsd.org mailing
Am 30.08.2011 19:57, schrieb Mark Linimon:
> On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote:
>> It only warns, it does not prevent fresh installs on systems that don't
>> have the same port/package already installed.
>
> "code, not policy" ... ?
Well... is _is_ policy and meant a
On Tue, 30 Aug 2011 11:24:43 -0500
Mark Linimon articulated:
> Could we please change the Subject line to match the content now?
That would probably not be the best idea. All things considered, the
new posts may well end up threaded along with the older posts. Starting
a entirely new post would b
On 08/30/2011 08:29, Chad Perrin wrote:
> On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote:
>> I'm doing some updates and came across mail/postfix-policyd-spf which
>> relies on mail/libspf2-10. The latter had a vuxml entry added on
>> 2008-10-27. So my question is, why has mail/libspf2-
Matthias Andree wrote:
Am 30.08.2011 18:40, schrieb Miroslav Lachman:
Hi,
[...]
So I have a question - why the rc script is not using required_modules
variable from /etc/rc.subr which is there exactly for this purpose?
Miroslav,
thanks for your required_modules suggestion. The script dat
On Tue, 30 Aug 2011, Matthias Andree wrote:
Am 30.08.2011 19:57, schrieb Mark Linimon:
On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote:
It only warns, it does not prevent fresh installs on systems that don't
have the same port/package already installed.
"code, not policy" ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 10:26 AM, Ruslan Mahmatkhanov wrote:
> Greg Larkin wrote on 30.08.2011 17:56:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote:
>>> Greg Larkin wrote on 30.08.2011 17:05:
-BEGIN
Greg Larkin wrote on 31.08.2011 00:07:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 10:26 AM, Ruslan Mahmatkhanov wrote:
Greg Larkin wrote on 30.08.2011 17:56:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote:
Greg Larkin wrote on 30.08.
Koop Mast wrote on 24.08.2011 16:20:
On Wed, 2011-08-24 at 14:45 +0400, Ruslan Mahmatkhanov wrote:
ajtiM wrote on 24.08.2011 14:38:
Stop in /usr/ports/graphics/gimp-gmic-plugin.
*** Error code 1
Stop in /usr/ports/graphics/gimp-gmic-plugin.
===>>> make failed for graphics/gimp-gmic-plugin
On Tue, Aug 30, 2011 at 11:55:25AM -0700, Doug Barton wrote:
> On 08/30/2011 08:29, Chad Perrin wrote:
> >
> > Might that not interfere with the process of getting a new maintainer for
> > a popular port when its previous maintainer has been lax (or hit by a
> > bus)?
>
> Sorry if I'm being dense
On 30 Aug 2011 22:13, "Chad Perrin" wrote:
>
> On Tue, Aug 30, 2011 at 11:55:25AM -0700, Doug Barton wrote:
> > On 08/30/2011 08:29, Chad Perrin wrote:
> > >
> > > Might that not interfere with the process of getting a new maintainer
for
> > > a popular port when its previous maintainer has been l
On Tuesday 30 August 2011 11:01:18 Ted Hatfield wrote:
> On Tue, 30 Aug 2011, Matthias Andree wrote:
> > Am 30.08.2011 19:57, schrieb Mark Linimon:
> >> On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote:
> >>> It only warns, it does not prevent fresh installs on systems that don't
> >
Matthias Andree wrote:
> I understand that keeping unchanging software can sometimes be
> necessary, if you're working around its quirks.
>
> At the same time I'd like to discourage new installations of dead
> software so that it disappears over time, rather than haunt fresh
> systems.
>
> How ab
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not subscribed to ports@, in the
Cc: list.
Date: Tue, 30 Aug 2011 13:52:12 +0100
Fr
Odd little problem here I'm noticing with cvs.
When I do a "cvs diff -uN", for some reason the -N switch is being
ignored. It vanishes completely in the header of the resulting
output. I've been trying to rename one of my patch files to conform to
portlint's recommendations, but unless I can get
In fact if use use_python=yes default is 27 we cant set python24 for removal
yet because we have fix first all zope stuff. Am back to the game after
Holiday
Sent from my iPhone
On Aug 30, 2011, at 21:56, Greg Larkin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 8/30/11 9:38
On Tue, 30 Aug 2011 19:51:14 -0500
"Conrad J. Sabatier" wrote:
> Incidentally, this problem started before I upgraded two days ago from
> 9.0-BETA1 to 9.0-BETA1, so it's not OS version-related.
^
|__ Errr, I meant "BETA2, of course :-)
--
Conrad J.
On Tue, 30 Aug 2011 18:06:15 +0200
Matthias Andree wrote:
> Once you have the necessary error handling in place in
> your .procmailrc, a .mailfilter file of equal usefulness in maildrop
> is shorter and more concise.
1. In the context of a FreeBSD port, there is absolutely nothing wrong
with mai
58 matches
Mail list logo
