Re: [Fink-devel] multiple notify plugins?

2006-12-08 Thread Dave Vasilevsky
On Dec 7, 2006, at 9:09 AM, Charles Lepple wrote: I was looking through the Fink/Notify.pm code, and it seems like only one plugin can be active at a time. I'm not well versed in Perl OOP, so I'm wondering if anyone knows of any architectural showstoppers for changing the NotifyPlugin co

Re: [Fink-devel] emacs22-carbon: upgrade to current cvs?

2006-12-08 Thread Alexander Hansen
On 12/8/06, Dean Scarff <[EMAIL PROTECTED]> wrote: > Alexander wrote: > > Since emacs-carbon is a maintained package, did you try contacting the > > listed maintainer? The general rule of thumb is that we don't tread > > on the toes of listed maintainers by updating their packages without > > cons

Re: [Fink-devel] boost1.33-1.33.1-1007

2006-12-08 Thread Martin Costabel
From: Alexander Hansen - 2006-12-05 01:52 > On 12/4/06, Jack Howarth wrote: >> Is anyone else seeing build failures with the new >> boost1.33-1.33.1-1007 packaging? I have a failure of... >> >> /bin/mv >> /sw/src/fink.build/root-boost1.33-1.33.1-1007/sw/lib/libboost_python-1_33_1.dylib >>

Re: [Fink-devel] multiple notify plugins?

2006-12-08 Thread Christian Schaffner
On 08.12.2006, at 06:38, Dave Vasilevsky wrote: > > On Dec 7, 2006, at 9:09 AM, Charles Lepple wrote: >> I was looking through the Fink/Notify.pm code, and it seems like only >> one plugin can be active at a time. I'm not well versed in Perl OOP, >> so I'm wondering if anyone knows of any

Re: [Fink-devel] multiple notify plugins?

2006-12-08 Thread Daniel Macks
On Fri, Dec 08, 2006 at 07:38:34AM -0500, Dave Vasilevsky wrote: > > On Dec 7, 2006, at 9:09 AM, Charles Lepple wrote: > >I was looking through the Fink/Notify.pm code, and it seems like only > >one plugin can be active at a time. I'm not well versed in Perl OOP, > >so I'm wondering if anyon

[Fink-devel] filenames for .info files

2006-12-08 Thread David R. Morrison
Starting in fink-0.26.0, there will be a new field "Distribution" which can be used to restrict a given file to only applying to the listed distribution(s). This will allow us to have the 10.4 and 10.5 distributions share a common set of packages. Sometimes, however, it will be necessary to