Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Daniel Staal
--As of April 29, 2012 8:11:19 PM +0100, RW is alleged to have said: So, is there any way to *avoid* getting that error? Some way where I can actually use the ports system to keep my stuff up to date? (Even if it doesn't include the manually-installed software?) It think you should be able

Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread RW
On Sun, 29 Apr 2012 12:25:39 -0400 Daniel Staal wrote: > So, is there any way to *avoid* getting that error? Some way where I > can actually use the ports system to keep my stuff up to date? (Even > if it doesn't include the manually-installed software?) It think you should be able to preven

Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Daniel Staal
--As of April 29, 2012 1:36:55 PM -0400, Jerry is alleged to have said: I will have a look at the CPAN module: CGI::Application::Plugin::CompressGzip later today or tomorrow and see if I can make a port of it for you. --As for the rest, it is mine. Sorry, I should have put this in the other e

Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Daniel Staal
--As of April 29, 2012 1:36:55 PM -0400, Jerry is alleged to have said: UNTESTED: In the /usr/local/etc/portmanager/pm-020.conf file, add the specific port(s) you are trying to bypass. EXAMPLE: IGNORE|www/tidy| Again, this is untested, but I have used it for other ports that I needed

Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Jerry
On Sun, 29 Apr 2012 13:23:23 -0400 Daniel Staal articulated: >--As of April 29, 2012 12:46:52 PM -0400, Jerry is alleged to have >said: > >>> Which would be fine, if annoying, if everything actually was >>> available in Ports. But it's not: I'm using several modules that >>> aren't available from

Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Daniel Staal
--As of April 29, 2012 12:46:52 PM -0400, Jerry is alleged to have said: Which would be fine, if annoying, if everything actually was available in Ports. But it's not: I'm using several modules that aren't available from Ports, and of course the modules I'm *developing* aren't available from Po

Re: bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Jerry
On Sun, 29 Apr 2012 12:25:39 -0400 Daniel Staal articulated: {SNIP} >Which would be fine, if annoying, if everything actually was available >in Ports. But it's not: I'm using several modules that aren't >available from Ports, and of course the modules I'm *developing* >aren't available from Port

bsdpan-* ports, portmanager, and "@comment ORIGIN:"

2012-04-29 Thread Daniel Staal
I'm working on developing some stuff in Perl on my box, which works fairly well unless I go to update my system. Anytime I do, I get the following error from portmanager: `rCreateInstalledDbVerifyContentsFile 0.4.1_9 error: "@comment ORIGIN:" not found in /var/db/pkg/bsdpan-$MODULE_NAME`