bsdpan-* ports, portmanager, and @comment ORIGIN:
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` Where $MODULE_NAME is one of the modules I've installed via CPAN, instead of using the FreeBSD ports system. It will advise me to delete the package and then try manually reinstalling it - which works, *if* I install the Ports version. Then running portmanager again will just pick the next module from the list, and go on, until I've uninstalled everything I installed via CPAN and installed it from Ports. 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 Ports. 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?) Or do I just have to avoid anything Perl-related from the Ports system and install everything manually? (Or - likely at that point - find a different OS to work on. It'd be less hassle to switch OSes than to try to make sure *nothing* using Perl is installed from the Ports.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
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 Ports.
Which specific modules are not available? In the past I had to port a
few Perl modules into FreeBSD or else install them via CPAN as you have
done. If it is a simple module, I can show you how to do it or make a
port for it myself. Also, you should be aware that many modules are
available in the ports system, but not under the correct CPAN name.
Don't ask why; I did once and got so much BS that I just abandoned the
question.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
--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 Ports. Which specific modules are not available? In the past I had to port a few Perl modules into FreeBSD or else install them via CPAN as you have done. If it is a simple module, I can show you how to do it or make a port for it myself. Also, you should be aware that many modules are available in the ports system, but not under the correct CPAN name. Don't ask why; I did once and got so much BS that I just abandoned the question. --As for the rest, it is mine. I'm still in early development, so the list is likely to grow as the project moves along. The main one that's causing me trouble at the moment is CGI::Application::Plugin::CompressGzip, although I've noticed that several others of the CGI::Application set that look interesting and useful aren't in the ports system. And, of course, there is the modules I'm developing for this project. Making ports for each one feels like a band-aid though: It's a 'solution' that's just going to grow in complexity and scope the longer it goes on, and isn't really fixing anything other than the individual symptoms. A real solution to me would either be a way to get @comment ORIGIN: to automatically populate in the bsdpan-* (CPAN) module install process, or a way to get portmanager to ignore modules installed via that process. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
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 Ports, and of course the modules I'm *developing* aren't available from Ports. Which specific modules are not available? In the past I had to port a few Perl modules into FreeBSD or else install them via CPAN as you have done. If it is a simple module, I can show you how to do it or make a port for it myself. Also, you should be aware that many modules are available in the ports system, but not under the correct CPAN name. Don't ask why; I did once and got so much BS that I just abandoned the question. --As for the rest, it is mine. I'm still in early development, so the list is likely to grow as the project moves along. The main one that's causing me trouble at the moment is CGI::Application::Plugin::CompressGzip, although I've noticed that several others of the CGI::Application set that look interesting and useful aren't in the ports system. And, of course, there is the modules I'm developing for this project. Making ports for each one feels like a band-aid though: It's a 'solution' that's just going to grow in complexity and scope the longer it goes on, and isn't really fixing anything other than the individual symptoms. A real solution to me would either be a way to get @comment ORIGIN: to automatically populate in the bsdpan-* (CPAN) module install process, or a way to get portmanager to ignore modules installed via that process. 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 to skip. 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. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
--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 to skip. --As for the rest, it is mine. Yes, that works for *ports.* Unfortunatly, it doesn't appear to work for non-ports that are installed but show up in the ports system. (The bsdpan-* stuff.) (Note: The error I quoted earlier is the very first thing that shows up when I run portmanager - it then goes on to collect installed port data, and notes but skips a couple that I had already put in to be ignored. The error I'm having appears to occur before that step - and interferes with the proper collection of installed port data.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
--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 email... While I'd thank you for the consideration and effort, I'd consider this time poorly spent: CGI::Application::Plugin::CompressGzip is not the problem, it's just the current showstopper symptom. The problem is the bsdpan system, which tries to integrate CPAN with the ports system. It needs to either: A. Work. or B. Get out of the way. If you want to spend time on this, please rather than create a band-aid, see if you can find the root problem in wherever the bsdpan system is, and submit a patch upstream (to whomever is in charge of that) to fix it. (Or remove it.) It might take a bit longer, but instead of fixing it for *me* *this week,* you'd fix it for *everyone* for quite a bit longer. I'm hoping someone on this list knows some of where that might be, or might even be the person to talk to in order to get it fixed. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
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 prevent the package entries by setting DISABLE_BSDPAN in the environment. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdpan-* ports, portmanager, and @comment ORIGIN:
--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 to prevent the package entries by setting DISABLE_BSDPAN in the environment. --As for the rest, it is mine. Semi-successful: It appears to work for `cpanp` installed modules, but not `cpan` installed modules. And for some reason, p5-CPANPLUS won't install correctly (no errors, it just doesn't actually install the client), so `cpanp` is a `cpan` installed module... (And yes, this is after reinstalling them.) So it looks like it's getting me partway there, but not all the way. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
