How to best handle ports mislinking against locally installed copies?
As an example, net/avahi-app fails to build on my machine because of the error: /libexec/ld-elf.so.1: Shared object libicui18n.so.38 not found, required by libavahi-glib.so.1 This can be fixed by removing the port before building so that it is unable to link against /usr/local/lib/libavahi-glib.so.1 and instead correctly links against ./work/avahi-0.6.29/avahi-glib/.libs/libavahi-glib.so.1 but is it correct to assume uninstall is needed before attempting to build a new version or are there suggested fixes or examples of working through this? I can try to dig up other examples I have ran into in detail but was wondering about the general approach and if the freebsd ports tree likes to fix it, note it, or ignore it? Thanks again, Edward Sanford Sutton, III ___ 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
Re: How to best handle ports mislinking against locally installed copies?
On Sat, Mar 26, 2011 at 02:29:14AM -0700, Edward Sanford Sutton, III wrote: As an example, net/avahi-app fails to build on my machine because of the error: /libexec/ld-elf.so.1: Shared object libicui18n.so.38 not found, required by libavahi-glib.so.1 This can be fixed by removing the port before building so that it is unable to link against /usr/local/lib/libavahi-glib.so.1 and instead correctly links against ./work/avahi-0.6.29/avahi-glib/.libs/libavahi-glib.so.1 but is it correct to assume uninstall is needed before attempting to build a new version or are there suggested fixes or examples of working through this? I can try to dig up other examples I have ran into in detail but was wondering about the general approach and if the freebsd ports tree likes to fix it, note it, or ignore it? These are usually documented in /usr/ports/UPDATING, so check it before updating ports. Usually a rebuild fixes the problem, but sometimes a lot of ports have to be reinstalled, so it is time consuming. Try out ports-mgmt/portmaster and use the -w flag to preserve libs. They will end up in /usr/local/lib/compat/pkg/lib/ until you decide to remove them. -- Denny Lin ___ 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
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
2011/3/25 Marcin Wisnicki mwisnicki+free...@gmail.com: On Fri, 25 Mar 2011 11:11:11 +0100, Baptiste Daroussin wrote: pkgng is a binary package manager written from scratch for FreeBSD. Fantastic! I know it is quite too early but I already have one feature request ;) Perhaps it could be added to the TODO as a post-1.0 goal. = Generic extraction filters = Allow registration of custom filters that can alter/exclude/add? files during package extraction (installation). Examples of possible filters: - strip debug info - exclude development files (headers, static libs) - exclude unused translations - exclude documentation (all or just unknown languages) - generic glob/regex path filters - optional file groups defined in package (install time OPTIONS) ? Some sort of configuration mechanism with list of enabled filters and their options (like a list of languages to keep). Most of this can be implemented as a simple glob/regex matching but there are edge cases where packages have some non-standard layout or have to keep certain file in which case a package metadata should contain a list of exclusions/additions from/to above categories. Package manager should register only actually installed files but list of alterations should be also kept somewhere in database. What do you think ? ___ 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 This can still be discussed but I don't really like the idea that users may alter packages an installation/extraction time, that would lead to lots of potential buggy installation and report. If user aren't happy with the packaging, they can poke the maintainer, send PR, patch etc. regards, Bapt ___ 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
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 12:11 PM, Baptiste Daroussin b...@freebsd.org wrote: Hi all, Hi, Great news! I'll try to contribute with what I can for this project! I've mirrored the pkgng Git repo here as well: - http://git.unix-heaven.org/cgit.cgi/pkgng/ And attached is my first patch :) Could you please review and if possible, apply it? Regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/ From bd17ad1dfa336717fcc924217552dadd5236ed5f Mon Sep 17 00:00:00 2001 From: Marin Atanasov Nikolov dae...@unix-heaven.org Date: Sat, 26 Mar 2011 14:19:04 +0200 Subject: [PATCH] Clarify a bit more the GOALS and some other minor changes - Clarify GOALS a bit more - Added main.h which contains CMD_MAX_LEN - Use strnlen() instead of strlen() in main.c - Use float numbers in fetch_status() --- docs/GOALS | 178 ++-- pkg/add.c |2 +- pkg/main.c |9 ++-- pkg/main.h |7 +++ 4 files changed, 126 insertions(+), 70 deletions(-) create mode 100644 pkg/main.h diff --git a/docs/GOALS b/docs/GOALS index 1c381d2..ccf3414 100644 --- a/docs/GOALS +++ b/docs/GOALS @@ -1,104 +1,152 @@ -comamnds: +pkgng - New version of FreeBSD's pkg_install + +Table of Contents: + +1. Available commands of pkgng +2. Available subcommands of pkgng +3. General behaviour +4. New manifest format + 4.1. During new install + 4.2. During package deletion + 4.3. During upgrade of a package +5. Additional resources + + +1. Available commands of pkgng: +--- + - pkg: - - one command to rule them all - - each time pkg has to query the installed database it will try to first - read the cache is the cache is too old (check but last mtime of the - directory) it will regenerate the cache from installed package + + - One command to rule them all + - Each time `pkg' has to query the package database it will try to first + read the cache and if the cache is too old (check by last mtime of the + directory) it will regenerate the cache for the installed packages. - pkg_*: - this will be shell script their goal is to be 100% compatible with - pkg_install they will call pkg which the good options (not sure it will - be really done in the end) -subcommands: + - These will be shell scripts, which goal is to be 100% compatible with + pkg_install. They will call `pkg' with the appropriate options (not sure + it will be really done in the end). + +2. Available subcommands of pkgng: +-- + - add: - - installs a package if local package is given - - manage http/ftp url to download throught libfetch a package and try to - install it. - - in the two previous case, if the package as not installed dependencies - it will try to fetch/find them in the same place the original package - was. - - it will manage a completely new repository format pkg add bla will - check in the database of the repository if the is a bla package and - install it as well as it's dependencies but the dependencies will be - compute before begining the fetch install process, to be sure - everything is ok. - - should be able to only take a plist or a manifest in argument + + - Installs a package if a local package is given + - Manages ftp/http downloads of packages through libfetch and + tries to install them. + - In the two previous cases, if a package does not have it's + dependencies installed, `pkgng' will try to fetch/find them in the same + place as the original package was. + - It will manage a completely new repository format. + `pkg add foo' will check in the database of the repository for + package foo and try to install it as well as it's dependencies. + Dependencies will be computed before beginning the fetch/install + process to ensure that everything will be OK. + - Should be able to only take a plist or a manifest in argument considering the files are already installed - repo: - - takes only one argument and generate two databases files (maybe more for - the time we will be willing to work with UPDATING and MOVED) the first - repo contain every informations concerning a package except files - (which will be in the second one) + it will compute and add a sha256 - sum for each package. - the database will be a sqlite file compressed with the xz format. - the database will be signed so we can trust the sha256 of the - packages, so if a package has the expected hash, it is considered + + - Takes only one argument and generates two database files (maybe more for + the time we will be willing to work with UPDATING and MOVED). + The first repo contains all information about a package, except for + the files (which will be in the second one) + it will compute and + add a sha256 sum for each package. + - The database will be a sqlite file compressed with the xz format. + - The database will be signed
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Sat, 26 Mar 2011 10:22:50 +, Baptiste Daroussin wrote: This can still be discussed but I don't really like the idea that users may alter packages an installation/extraction time, that would lead to lots of potential buggy installation and report. That's why list of alterations have to be recorded and relevant tools would mark such packages appropriately. Using filters would be considered unsupported (unless maintainer of particular port/package says otherwise). It's no different than doing unsupported things right now, just giving user more tools. Besides, examples mentioned by me like removing docs and unused translations are rather safe and save significant amount of disk space. If user aren't happy with the packaging, they can poke the maintainer, send PR, patch etc. That's not possible unless user is willing to build packages himself. Actually I would rather not have build time options for things that can just as well be performed during installation. Hacking makefiles to implement NOPORTDOCS is quite more complicated than setting a glob pattern. There is also one very important use case I didn't mention before. Such filters could serve as a hooking point for configuration management system. It makes it possible to capture config files as they are installed and perform backups, merges, check-in to vcs etc. regards, Bapt ___ 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 ___ 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
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
This can still be discussed but I don't really like the idea that users may alter packages an installation/extraction time, that would lead to lots of potential buggy installation and report. If user aren't happy with the packaging, they can poke the maintainer, send PR, patch etc. The whole point of *binary* packages is that people don't mess changing options, changing what is installed, etc. so that port maintainers know exactly what people have on their machine, and be able to test it. This is a prerequisite for a system which is not a complete mess. Those you like to change things are on their own. -- Michel TALON ___ 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
Updating multiple ports with portmaster
I have a questions about the use of portmaster when upgrading multiple ports and how to correctly use wildcards. For example, I have this from pkg_version: p5-Digest-SHA-5.50 needs updating (port has 5.61) p5-IO-Socket-SSL-1.38 needs updating (port has 1.39) p5-IPC-Cmd-0.68needs updating (port has 0.70) p5-Math-BigInt-1.99needs updating (port has 1.993) p5-Module-Build-0.3607_1 needs updating (port has 0.3624) p5-Module-CoreList-2.42needs updating (port has 2.45) p5-Module-Load-Conditional-0.38needs updating (port has 0.44) p5-Params-Check-0.26_1 needs updating (port has 0.28) p5-Test-Harness-3.22 needs updating (port has 3.23) p5-URI-1.56needs updating (port has 1.58) When I was using portupgrade, I could type... portupgrade p5-* ...and it would upgrade only the ports that needed upgrading and dependancies. But if I try... portmaster p5-* === The following actions will be taken if you choose to proceed: Re-install p5-Digest-SHA1-2.13 Re-install p5-IO-Compress-2.033 Re-install p5-Compress-Raw-Bzip2-2.033 Re-install p5-Compress-Raw-Zlib-2.033 Re-install p5-HTML-Tagset-3.20 Re-install p5-HTML-Parser-3.68 Upgrade p5-Digest-SHA-5.50 to p5-Digest-SHA-5.61 Re-install p5-Mail-SpamAssassin-3.3.1_3 Re-install p5-Archive-Tar-1.76 Re-install p5-IO-Zlib-1.10_1 Re-install p5-IO-String-1.08 Re-install p5-Package-Constants-0.02 Re-install p5-Encode-Detect-1.01 Re-install p5-ExtUtils-CBuilder-0.2802_1,1 Upgrade p5-IPC-Cmd-0.68 to p5-IPC-Cmd-0.70 Re-install p5-Locale-Maketext-Simple-0.21 Upgrade p5-Module-Load-Conditional-0.38 to p5-Module-Load-Conditional-0.44 Upgrade p5-Module-CoreList-2.42 to p5-Module-CoreList-2.45 Re-install p5-Module-Load-0.18 Upgrade p5-Params-Check-0.26_1 to p5-Params-Check-0.28 Re-install p5-version-0.88 Upgrade p5-Module-Build-0.3607_1 to p5-Module-Build-0.3624 Install devel/p5-CPAN-Meta-YAML Re-install p5-ExtUtils-Install-1.54 Re-install p5-ExtUtils-ParseXS-2.22.03 Install devel/p5-Module-Metadata Install devel/p5-Perl-OSType Upgrade p5-Test-Harness-3.22 to p5-Test-Harness-3.23 Re-install p5-Net-DNS-0.66_1 Re-install p5-Net-IP-1.25_2 Re-install p5-IO-Socket-INET6-2.65 Re-install p5-Socket6-0.23 Re-install p5-Digest-HMAC-1.02 Re-install p5-Mail-Tools-2.07 Re-install p5-TimeDate-1.20,1 Re-install p5-NetAddr-IP-4.038 Upgrade p5-IO-Socket-SSL-1.38 to p5-IO-Socket-SSL-1.39 Re-install p5-Net-SSLeay-1.36 Re-install p5-libwww-5.837 Upgrade p5-URI-1.56 to p5-URI-1.58 Re-install p5-YAML-Tiny-1.44 Re-install p5-Time-HiRes-1.9721,1 Re-install p5-Locale-gettext-1.05_3 Upgrade p5-Math-BigInt-1.99 to p5-Math-BigInt-1.993 Re-install p5-ExtUtils-MakeMaker-6.56 Re-install p5-MIME-Base64-3.13 Re-install p5-YAML-0.72 Re-install p5-Error-0.17016 Re-install p5-Net-DNS-Resolver-Programmable-0.003 Re-install p5-Mail-SPF-2.007 ...it wants to upgrade and reinstall every port that I have installed that begins with p5-* Is there a way to get portmaster to behave like portupgrade did and only upgrade what needs to be upgraded? Thanks, Ron ___ 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
Re: Updating multiple ports with portmaster
On 3/26/2011 8:22 AM, Ron (Lists) wrote: I have a questions about the use of portmaster when upgrading multiple ports and how to correctly use wildcards. For example, I have this from pkg_version: p5-Digest-SHA-5.50 needs updating (port has 5.61) p5-IO-Socket-SSL-1.38 needs updating (port has 1.39) p5-IPC-Cmd-0.68 needs updating (port has 0.70) p5-Math-BigInt-1.99 needs updating (port has 1.993) p5-Module-Build-0.3607_1 needs updating (port has 0.3624) p5-Module-CoreList-2.42 needs updating (port has 2.45) p5-Module-Load-Conditional-0.38 needs updating (port has 0.44) p5-Params-Check-0.26_1 needs updating (port has 0.28) p5-Test-Harness-3.22 needs updating (port has 3.23) p5-URI-1.56 needs updating (port has 1.58) When I was using portupgrade, I could type... portupgrade p5-* ...and it would upgrade only the ports that needed upgrading and dependancies. But if I try... portmaster p5-* === The following actions will be taken if you choose to proceed: Re-install p5-Digest-SHA1-2.13 Re-install p5-IO-Compress-2.033 Re-install p5-Compress-Raw-Bzip2-2.033 Re-install p5-Compress-Raw-Zlib-2.033 Re-install p5-HTML-Tagset-3.20 Re-install p5-HTML-Parser-3.68 Upgrade p5-Digest-SHA-5.50 to p5-Digest-SHA-5.61 Re-install p5-Mail-SpamAssassin-3.3.1_3 Re-install p5-Archive-Tar-1.76 Re-install p5-IO-Zlib-1.10_1 Re-install p5-IO-String-1.08 Re-install p5-Package-Constants-0.02 Re-install p5-Encode-Detect-1.01 Re-install p5-ExtUtils-CBuilder-0.2802_1,1 Upgrade p5-IPC-Cmd-0.68 to p5-IPC-Cmd-0.70 Re-install p5-Locale-Maketext-Simple-0.21 Upgrade p5-Module-Load-Conditional-0.38 to p5-Module-Load-Conditional-0.44 Upgrade p5-Module-CoreList-2.42 to p5-Module-CoreList-2.45 Re-install p5-Module-Load-0.18 Upgrade p5-Params-Check-0.26_1 to p5-Params-Check-0.28 Re-install p5-version-0.88 Upgrade p5-Module-Build-0.3607_1 to p5-Module-Build-0.3624 Install devel/p5-CPAN-Meta-YAML Re-install p5-ExtUtils-Install-1.54 Re-install p5-ExtUtils-ParseXS-2.22.03 Install devel/p5-Module-Metadata Install devel/p5-Perl-OSType Upgrade p5-Test-Harness-3.22 to p5-Test-Harness-3.23 Re-install p5-Net-DNS-0.66_1 Re-install p5-Net-IP-1.25_2 Re-install p5-IO-Socket-INET6-2.65 Re-install p5-Socket6-0.23 Re-install p5-Digest-HMAC-1.02 Re-install p5-Mail-Tools-2.07 Re-install p5-TimeDate-1.20,1 Re-install p5-NetAddr-IP-4.038 Upgrade p5-IO-Socket-SSL-1.38 to p5-IO-Socket-SSL-1.39 Re-install p5-Net-SSLeay-1.36 Re-install p5-libwww-5.837 Upgrade p5-URI-1.56 to p5-URI-1.58 Re-install p5-YAML-Tiny-1.44 Re-install p5-Time-HiRes-1.9721,1 Re-install p5-Locale-gettext-1.05_3 Upgrade p5-Math-BigInt-1.99 to p5-Math-BigInt-1.993 Re-install p5-ExtUtils-MakeMaker-6.56 Re-install p5-MIME-Base64-3.13 Re-install p5-YAML-0.72 Re-install p5-Error-0.17016 Re-install p5-Net-DNS-Resolver-Programmable-0.003 Re-install p5-Mail-SPF-2.007 ...it wants to upgrade and reinstall every port that I have installed that begins with p5-* Is there a way to get portmaster to behave like portupgrade did and only upgrade what needs to be upgraded? Not directly. You could mimic the behavior using the -i option with either 'portmaster -a' or 'portmaster p5-'. And to answer your likely followup question, I have no plans to add such an option. :) hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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
Re: Updating multiple ports with portmaster
I have a questions about the use of portmaster when upgrading multiple ports and how to correctly use wildcards. For example, I have this from pkg_version: p5-Digest-SHA-5.50 needs updating (port has 5.61) p5-IO-Socket-SSL-1.38 needs updating (port has 1.39) p5-IPC-Cmd-0.68needs updating (port has 0.70) p5-Math-BigInt-1.99needs updating (port has 1.993) p5-Module-Build-0.3607_1 needs updating (port has 0.3624) p5-Module-CoreList-2.42needs updating (port has 2.45) p5-Module-Load-Conditional-0.38needs updating (port has 0.44) p5-Params-Check-0.26_1 needs updating (port has 0.28) p5-Test-Harness-3.22 needs updating (port has 3.23) p5-URI-1.56needs updating (port has 1.58) When I was using portupgrade, I could type... portupgrade p5-* ...and it would upgrade only the ports that needed upgrading and dependancies. But if I try... portmaster p5-* === The following actions will be taken if you choose to proceed: Re-install p5-Digest-SHA1-2.13 Re-install p5-IO-Compress-2.033 Re-install p5-Compress-Raw-Bzip2-2.033 Re-install p5-Compress-Raw-Zlib-2.033 Re-install p5-HTML-Tagset-3.20 Re-install p5-HTML-Parser-3.68 Upgrade p5-Digest-SHA-5.50 to p5-Digest-SHA-5.61 Re-install p5-Mail-SpamAssassin-3.3.1_3 Re-install p5-Archive-Tar-1.76 Re-install p5-IO-Zlib-1.10_1 Re-install p5-IO-String-1.08 Re-install p5-Package-Constants-0.02 Re-install p5-Encode-Detect-1.01 Re-install p5-ExtUtils-CBuilder-0.2802_1,1 Upgrade p5-IPC-Cmd-0.68 to p5-IPC-Cmd-0.70 Re-install p5-Locale-Maketext-Simple-0.21 Upgrade p5-Module-Load-Conditional-0.38 to p5-Module-Load-Conditional-0.44 Upgrade p5-Module-CoreList-2.42 to p5-Module-CoreList-2.45 Re-install p5-Module-Load-0.18 Upgrade p5-Params-Check-0.26_1 to p5-Params-Check-0.28 Re-install p5-version-0.88 Upgrade p5-Module-Build-0.3607_1 to p5-Module-Build-0.3624 Install devel/p5-CPAN-Meta-YAML Re-install p5-ExtUtils-Install-1.54 Re-install p5-ExtUtils-ParseXS-2.22.03 Install devel/p5-Module-Metadata Install devel/p5-Perl-OSType Upgrade p5-Test-Harness-3.22 to p5-Test-Harness-3.23 Re-install p5-Net-DNS-0.66_1 Re-install p5-Net-IP-1.25_2 Re-install p5-IO-Socket-INET6-2.65 Re-install p5-Socket6-0.23 Re-install p5-Digest-HMAC-1.02 Re-install p5-Mail-Tools-2.07 Re-install p5-TimeDate-1.20,1 Re-install p5-NetAddr-IP-4.038 Upgrade p5-IO-Socket-SSL-1.38 to p5-IO-Socket-SSL-1.39 Re-install p5-Net-SSLeay-1.36 Re-install p5-libwww-5.837 Upgrade p5-URI-1.56 to p5-URI-1.58 Re-install p5-YAML-Tiny-1.44 Re-install p5-Time-HiRes-1.9721,1 Re-install p5-Locale-gettext-1.05_3 Upgrade p5-Math-BigInt-1.99 to p5-Math-BigInt-1.993 Re-install p5-ExtUtils-MakeMaker-6.56 Re-install p5-MIME-Base64-3.13 Re-install p5-YAML-0.72 Re-install p5-Error-0.17016 Re-install p5-Net-DNS-Resolver-Programmable-0.003 Re-install p5-Mail-SPF-2.007 ...it wants to upgrade and reinstall every port that I have installed that begins with p5-* Is there a way to get portmaster to behave like portupgrade did and only upgrade what needs to be upgraded? This is documented in the portmaster(1) manpage. You can use -a to update all ports that need to be updated. To update a subset of those, you could (1) use -i with -a or a glob (by the way, the * isn't needed with portmaster -- see the portmaster(1) manpage), and respond in the negative to prompts to update or re-install those you wish to exclude; (2) use -x with -a or a glob, to exclude certain ports; or (3) feed portmaster a list of globs that match only those ports that you want to be updated. In your case, for (3), if you only wanted to update those p5-* ports that need to be updated, but not other ports that need to be updated, you could use something like: pkg_version -qos p5- -l '' | xargs portmaster Of course, since some new versions of p5-* ports may depend upon new versions of other, non p5-* ports, updating only the p5-* ports isn't guaranteed to work. b. ___ 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
Re: Updating multiple ports with portmaster
On 26/03/2011 16:47, Doug Barton wrote:
On 3/26/2011 8:22 AM, Ron (Lists) wrote:
I have a questions about the use of portmaster when upgrading multiple
ports and how to correctly use wildcards.
For example, I have this from pkg_version:
p5-Digest-SHA-5.50 needs updating (port has 5.61)
p5-IO-Socket-SSL-1.38 needs updating (port has 1.39)
p5-IPC-Cmd-0.68 needs updating (port has 0.70)
p5-Math-BigInt-1.99 needs updating (port has 1.993)
p5-Module-Build-0.3607_1 needs updating (port has 0.3624)
p5-Module-CoreList-2.42 needs updating (port has 2.45)
p5-Module-Load-Conditional-0.38 needs updating (port has 0.44)
p5-Params-Check-0.26_1 needs updating (port has 0.28)
p5-Test-Harness-3.22 needs updating (port has 3.23)
p5-URI-1.56 needs updating (port has 1.58)
When I was using portupgrade, I could type...
portupgrade p5-*
...and it would upgrade only the ports that needed upgrading and
dependancies. But if I try...
portmaster p5-*
=== The following actions will be taken if you choose to proceed:
Re-install p5-Digest-SHA1-2.13
Re-install p5-IO-Compress-2.033
Re-install p5-Compress-Raw-Bzip2-2.033
Re-install p5-Compress-Raw-Zlib-2.033
Re-install p5-HTML-Tagset-3.20
Re-install p5-HTML-Parser-3.68
Upgrade p5-Digest-SHA-5.50 to p5-Digest-SHA-5.61
Re-install p5-Mail-SpamAssassin-3.3.1_3
Re-install p5-Archive-Tar-1.76
Re-install p5-IO-Zlib-1.10_1
Re-install p5-IO-String-1.08
Re-install p5-Package-Constants-0.02
Re-install p5-Encode-Detect-1.01
Re-install p5-ExtUtils-CBuilder-0.2802_1,1
Upgrade p5-IPC-Cmd-0.68 to p5-IPC-Cmd-0.70
Re-install p5-Locale-Maketext-Simple-0.21
Upgrade p5-Module-Load-Conditional-0.38 to
p5-Module-Load-Conditional-0.44
Upgrade p5-Module-CoreList-2.42 to p5-Module-CoreList-2.45
Re-install p5-Module-Load-0.18
Upgrade p5-Params-Check-0.26_1 to p5-Params-Check-0.28
Re-install p5-version-0.88
Upgrade p5-Module-Build-0.3607_1 to p5-Module-Build-0.3624
Install devel/p5-CPAN-Meta-YAML
Re-install p5-ExtUtils-Install-1.54
Re-install p5-ExtUtils-ParseXS-2.22.03
Install devel/p5-Module-Metadata
Install devel/p5-Perl-OSType
Upgrade p5-Test-Harness-3.22 to p5-Test-Harness-3.23
Re-install p5-Net-DNS-0.66_1
Re-install p5-Net-IP-1.25_2
Re-install p5-IO-Socket-INET6-2.65
Re-install p5-Socket6-0.23
Re-install p5-Digest-HMAC-1.02
Re-install p5-Mail-Tools-2.07
Re-install p5-TimeDate-1.20,1
Re-install p5-NetAddr-IP-4.038
Upgrade p5-IO-Socket-SSL-1.38 to p5-IO-Socket-SSL-1.39
Re-install p5-Net-SSLeay-1.36
Re-install p5-libwww-5.837
Upgrade p5-URI-1.56 to p5-URI-1.58
Re-install p5-YAML-Tiny-1.44
Re-install p5-Time-HiRes-1.9721,1
Re-install p5-Locale-gettext-1.05_3
Upgrade p5-Math-BigInt-1.99 to p5-Math-BigInt-1.993
Re-install p5-ExtUtils-MakeMaker-6.56
Re-install p5-MIME-Base64-3.13
Re-install p5-YAML-0.72
Re-install p5-Error-0.17016
Re-install p5-Net-DNS-Resolver-Programmable-0.003
Re-install p5-Mail-SPF-2.007
...it wants to upgrade and reinstall every port that I have installed
that begins with p5-*
Is there a way to get portmaster to behave like portupgrade did and only
upgrade what needs to be upgraded?
Not directly. You could mimic the behavior using the -i option with
either 'portmaster -a' or 'portmaster p5-'. And to answer your likely
followup question, I have no plans to add such an option. :)
pkg_version -vIL= | awk '/^p5-/ { print $1 }' | xargs portmaster
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Can't start X after update
Hello FreeBSD I updated the below listed ports on one of my systems today using portmaster. The system is running 9.0 Current updated yesterday. [robert@9BSD64] ~ uname -a FreeBSD 9BSD64.shasta204.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Fri Mar 25 11:31:42 PDT 2011 root@9BSD64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 goffice-0.8.14 libgsf-1.14.20 libgsf-gnome-1.14.20 xf86-video-ati-6.14.1 gnumeric-1.10.14 After updating these ports, I am unable to start an XFCE4 session. I get a blank blue screen with a mouse cursor and a blank white task bar. The system is locked up. I cannot even ctl-alt-F2 or even ctl-alt-del. The keyboard and mouse are unresponsive. I can ssh into the system and then I really see some weird stuff. Top does not even show that I have executed the startx command. last pid: 2632; load averages: 0.00, 0.00, 0.02 up 0+00:19:19 09:44:39 63 processes: 1 running, 62 sleeping CPU: 0.0% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.6% idle Mem: 28M Active, 33M Inact, 130M Wired, 92K Cache, 72M Buf, 3703M Free Swap: 4096M Total, 4096M Free PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 2445 haldaemon 2 200 40300K 9160K piperd 0 0:01 0.00% hald 2451 root 1 370 19616K 2964K select 0 0:00 0.00% gam_server 2471 root 1 200 19964K 2124K select 0 0:00 0.00% hald-addon-storage 2474 root 1 200 19964K 2124K select 0 0:00 0.00% hald-addon-storage 2452 root 1 520 24520K 3472K select 1 0:00 0.00% hald-runner 2087 root 1 200 22448K 3208K select 0 0:00 0.00% ntpd 2447 root 18 200 50824K 7432K waitvt 1 0:00 0.00% console-kit-daemon 2449 root 2 200 41488K 6712K select 0 0:00 0.00% polkitd 2588 root 1 210 68072K 5480K sbwait 1 0:00 0.00% sshd 1987 root 1 520 10052K 1820K select 0 0:00 0.00% nfsd 2459 root 1 200 19964K 2116K select 0 0:00 0.00% hald-addon-storage 2604 robert1 200 16616K 3160K pause 0 0:00 0.00% csh 2504 robert1 310 16616K 3200K ttyin 1 0:00 0.00% csh 2603 robert1 200 68072K 5516K select 1 0:00 0.00% sshd 2458 root 1 520 24188K 3020K kqread 1 0:00 0.00% hald-addon-mouse-sy 2279 root 1 200 20508K 4044K select 0 0:00 0.00% sendmail 2433 root 1 200 41260K 2328K wait1 0:00 0.00% login 1844 root 1 200 12312K 1672K select 0 0:00 0.00% syslogd 2168 messagebus1 200 1K 2480K select 0 0:00 0.00% dbus-daemon 1985 root 1 200 12180K 2132K select 0 0:00 0.00% mountd 1870 root 1 200 14264K 1792K select 1 0:00 0.00% rpcbind 2014 root 1 380 24984K 3344K nanslp 0 0:00 0.00% smartd 2340 root 1 520 14388K 1776K nanslp 1 0:00 0.00% cron 2632 robert1 200 16700K 2448K CPU11 0:00 0.00% top 1988 root 4 200 10052K 1360K rpcsvc 1 0:00 0.00% nfsd 2050 root 1 520 10196K 1668K select 1 0:00 0.00% lpd 2440 root 1 520 12184K 1404K ttyin 1 0:00 0.00% getty 2435 root 1 520 12184K 1404K ttyin 1 0:00 0.00% getty 2436 root 1 520 12184K 1404K ttyin 1 0:00 0.00% getty 2439 root 1 520 12184K 1404K ttyin 0 0:00 0.00% getty 2434 root 1 520 12184K 1404K ttyin 0 0:00 0.00% getty 2437 root 1 520 12184K 1404K ttyin 0 0:00 0.00% getty 2438 root 1 520 12184K 1404K ttyin 1 0:00 0.00% getty 2221 root 1 200 46932K 4716K select 1 0:00 0.00% sshd 2144 root 1 200 14364K 1468K select 1 0:00 0.00% moused 2333 smmsp 1 220 20508K 4136K pause 0 0:00 0.00% sendmail 2377 root 1 320 11220K 1756K select 0 0:00 0.00% rsync 1498 root 1 520 10052K 1664K select 0 0:00 0.00% dhclient 1537 root 1 200 6276K 840K select 0 0:00 0.00% devd 1536 _dhcp 1 200 10052K 1768K select 0 0:00 0.00% dhclient 2549 robert1 520 36208K 4056K select 1 0:00 0.00% ssh-agent I normally do not run HAL but I enabled it in rc.conf to see if it made a difference. Obviously it did not. Using ps axw also show nothing X related as running. Anyone seeing this or have an idea of what to try? TIA Robert ___ 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
Re: Updating multiple ports with portmaster
Am 26.03.2011 17:58, schrieb b. f.: I have a questions about the use of portmaster when upgrading multiple ports and how to correctly use wildcards. For example, I have this from pkg_version: p5-Digest-SHA-5.50needs updating (port has 5.61) p5-IO-Socket-SSL-1.38needs updating (port has 1.39) p5-IPC-Cmd-0.68needs updating (port has 0.70) p5-Math-BigInt-1.99needs updating (port has 1.993) p5-Module-Build-0.3607_1needs updating (port has 0.3624) p5-Module-CoreList-2.42needs updating (port has 2.45) p5-Module-Load-Conditional-0.38needs updating (port has 0.44) p5-Params-Check-0.26_1needs updating (port has 0.28) p5-Test-Harness-3.22needs updating (port has 3.23) p5-URI-1.56needs updating (port has 1.58) When I was using portupgrade, I could type... portupgrade p5-* ...and it would upgrade only the ports that needed upgrading and dependancies. But if I try... portmaster p5-* === The following actions will be taken if you choose to proceed: Re-install p5-Digest-SHA1-2.13 Re-install p5-IO-Compress-2.033 Re-install p5-Compress-Raw-Bzip2-2.033 Re-install p5-Compress-Raw-Zlib-2.033 Re-install p5-HTML-Tagset-3.20 Re-install p5-HTML-Parser-3.68 Upgrade p5-Digest-SHA-5.50 to p5-Digest-SHA-5.61 Re-install p5-Mail-SpamAssassin-3.3.1_3 Re-install p5-Archive-Tar-1.76 Re-install p5-IO-Zlib-1.10_1 Re-install p5-IO-String-1.08 Re-install p5-Package-Constants-0.02 Re-install p5-Encode-Detect-1.01 Re-install p5-ExtUtils-CBuilder-0.2802_1,1 Upgrade p5-IPC-Cmd-0.68 to p5-IPC-Cmd-0.70 Re-install p5-Locale-Maketext-Simple-0.21 Upgrade p5-Module-Load-Conditional-0.38 to p5-Module-Load-Conditional-0.44 Upgrade p5-Module-CoreList-2.42 to p5-Module-CoreList-2.45 Re-install p5-Module-Load-0.18 Upgrade p5-Params-Check-0.26_1 to p5-Params-Check-0.28 Re-install p5-version-0.88 Upgrade p5-Module-Build-0.3607_1 to p5-Module-Build-0.3624 Install devel/p5-CPAN-Meta-YAML Re-install p5-ExtUtils-Install-1.54 Re-install p5-ExtUtils-ParseXS-2.22.03 Install devel/p5-Module-Metadata Install devel/p5-Perl-OSType Upgrade p5-Test-Harness-3.22 to p5-Test-Harness-3.23 Re-install p5-Net-DNS-0.66_1 Re-install p5-Net-IP-1.25_2 Re-install p5-IO-Socket-INET6-2.65 Re-install p5-Socket6-0.23 Re-install p5-Digest-HMAC-1.02 Re-install p5-Mail-Tools-2.07 Re-install p5-TimeDate-1.20,1 Re-install p5-NetAddr-IP-4.038 Upgrade p5-IO-Socket-SSL-1.38 to p5-IO-Socket-SSL-1.39 Re-install p5-Net-SSLeay-1.36 Re-install p5-libwww-5.837 Upgrade p5-URI-1.56 to p5-URI-1.58 Re-install p5-YAML-Tiny-1.44 Re-install p5-Time-HiRes-1.9721,1 Re-install p5-Locale-gettext-1.05_3 Upgrade p5-Math-BigInt-1.99 to p5-Math-BigInt-1.993 Re-install p5-ExtUtils-MakeMaker-6.56 Re-install p5-MIME-Base64-3.13 Re-install p5-YAML-0.72 Re-install p5-Error-0.17016 Re-install p5-Net-DNS-Resolver-Programmable-0.003 Re-install p5-Mail-SPF-2.007 ...it wants to upgrade and reinstall every port that I have installed that begins with p5-* Is there a way to get portmaster to behave like portupgrade did and only upgrade what needs to be upgraded? This is documented in the portmaster(1) manpage. You can use -a to update all ports that need to be updated. To update a subset of those, you could (1) use -i with -a or a glob (by the way, the * isn't needed with portmaster -- see the portmaster(1) manpage), and respond in the negative to prompts to update or re-install those you wish to exclude; (2) use -x with -a or a glob, to exclude certain ports; or (3) feed portmaster a list of globs that match only those ports that you want to be updated. In your case, for (3), if you only wanted to update those p5-* ports that need to be updated, but not other ports that need to be updated, you could use something like: pkg_version -qos p5- -l '' | xargs portmaster Of course, since some new versions of p5-* ports may depend upon new versions of other, non p5-* ports, updating only the p5-* ports isn't guaranteed to work. portmaster takes care of that, except if there are downstream dependencies that stop working with updated ports on your list -- but that's rather rarely observed and usually documented in /usr/ports/UPDATING -- but even then, portmaster -a -i would likely help. -- Matthias Andree ___ 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
Re: Can't start X after update
On Sat, 26 Mar 2011 09:51:58 -0700 Robert travelin...@cox.net wrote: I updated the below listed ports on one of my systems today using portmaster. The system is running 9.0 Current updated yesterday. [robert@9BSD64] ~ uname -a FreeBSD 9BSD64.shasta204.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Fri Mar 25 11:31:42 PDT 2011 root@9BSD64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 goffice-0.8.14 libgsf-1.14.20 libgsf-gnome-1.14.20 xf86-video-ati-6.14.1 ^ It's probably this. Several users have reported problems caused by it on x...@freebsd.org. Take a look at this http://lists.freebsd.org/pipermail/freebsd-x11/2011-March/010737.html gnumeric-1.10.14 -- Gary Jennejohn ___ 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
Re: Can't start X after update
On Sat, 26 Mar 2011 19:22:30 +0100 Gary Jennejohn gljennj...@googlemail.com wrote: On Sat, 26 Mar 2011 09:51:58 -0700 Robert travelin...@cox.net wrote: I updated the below listed ports on one of my systems today using portmaster. The system is running 9.0 Current updated yesterday. [robert@9BSD64] ~ uname -a FreeBSD 9BSD64.shasta204.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Fri Mar 25 11:31:42 PDT 2011 root@9BSD64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 goffice-0.8.14 libgsf-1.14.20 libgsf-gnome-1.14.20 xf86-video-ati-6.14.1 ^ It's probably this. Several users have reported problems caused by it on x...@freebsd.org. Take a look at this http://lists.freebsd.org/pipermail/freebsd-x11/2011-March/010737.html gnumeric-1.10.14 Gary Thanks for the link. Further testing showed that changing driver to VESA worked fine. So I was sure it was the ati update. Robert ___ 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
Re: Can't start X after update
Robert travelin...@cox.net wrote: I updated the below listed ports on one of my systems today using portmaster. The system is running 9.0 Current updated yesterday. After updating these ports, I am unable to start an XFCE4 session. I get a blank blue screen with a mouse cursor and a blank white task bar. The system is locked up. I cannot even ctl-alt-F2 or even ctl-alt-del. Probably a problem with xf86-video-ati 6.14.1. Could be this one: http://docs.freebsd.org/cgi/mid.cgi?201103251935.27259.jkim -- Christian naddy Weisgerber na...@mips.inka.de ___ 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
some vdr intro/installation notes (watch/record/stream tv)
Hi, now that the vdr ports are finally committed here are some updated notes: So what is vdr? It's something like a luxury settop box/pvr on a pc to receive/watch/record/stream digital tv channels with epg (electronic program guide), timers, client/server networking, webinterface etc pp. So if you have a FreeBSD (or Linux, but that's not covered here :) server you can add one or more dvb/atsc tuner(s) connected to a satellite dish, cable tv or just a dvb-t antenna (or receive iptv streams without a tuner if your isp provides those tho I don't know if anyone tested `real' iptv on FreeBSD yet), browse/search epg, set timers for automated or manual recordings, and watch the streams/recordings elsewhere on your lan. Or if you have a FreeBSD desktop you can also connect a tuner there and do it all on one box - or just run a vdr client like vdr-sxfe (installed by the multimedia/vdr-plugin-xineliboutput port) or a client vdr instance using the streamdev-client plugin connected to a (possibly Linux) vdr server elsewhere on your lan. So if your isp doesn't provide iptv, https://secure.wikimedia.org/wikipedia/en/wiki/IPTV (german info page: http://www.iptv-anbieter.info/ ) then you'll need a dvb tuner (or atsc, tho I have no idea if anyone tested that with vdr on FreeBSD yet) with corresponding v4l/dvb (`v4b') drivers, in most cases that means an usb tuner supported by the webcamd port: http://www.freshports.org/multimedia/webcamd And finally, if you want to compare vdr to other existing ports, it's a bit like mythtv - only most Linux users _I_ know prefer vdr over mythtv. :) (and vdr also doesn't use a rdbms so you don't have to worry about mysql etc.) snip---previous-notes-with-minor-updates:--- I started with jpulz' vdr 1.7.14 patches: (now updated to 1.7.17) ftp://ftp.frm2.tum.de/pub/jpulz/VDR/ ftp://ftp.frm2.tum.de/pub/jpulz/pictures/ and made qd ports of those and of a few more plugins and two webinterfaces so I can now use FreeBSD as a pc hdtv dvb-s2 and also dvb-t dvr. Note: vdr 1.7.17 is the development branch so expect bugs! (I mostly used it because the stable branch (1.6) doesn't support dvb-s2 and h264...) FreeBSD notes: 0. See my earlier threads on the freebsd-multimedia list about webcamd and the usb dvb-s2 and dvb-t tuners I tested; the relevant webcamd ports and frieds have been updated now so you _should_ be able to just use those. (dvb-c or atsc(?) tuners should also work as long as webcamd supports them and there aren't other bugs.) Links to the more important posts are also here: http://people.freebsd.org/~nox/dvb/ 1. Before you start installing these ports either mount an extra fs with enough space for the recordings on /video or create a video dir elsewhere where there is space, symlink it to /video and make it writable for the vdr user. (or if you do have one big / then you can create the dir on there too of course, I just disabled the mkdir in the port to avoid inadvertently filling up ppl's small / fs.) Or if you don't like a symlink you can also add your video dir as -v dir to vdr's startup args, see below. 2. There is a multimedia/vdr-plugins metaport that allows you to select and install the plugins you want (and vdr itself as a dependency), so you don't have to install numerous vdr/plugin ports individually. 3. I have rc.d scripts for vdr and vdradmin-am but even if you use those you still need to add plugins and their options similar to this to your /etc/rc.conf: ---snip # vdr vdr_flags='-Pxineliboutput --local=none --remote=127.1:37890' \ -Pskinenigmang -Pfemon -Posdpip \ '-Posdteletext --cache-system=packed --max-cache=128' \ -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol \ -Pinfosatepg -Piptv '-Pupnp -i lo0' ---snip look in the README.s of the individual plugin ports for any needed options. (should get installed below /usr/local/share/doc/vdr*) And if you want vdr to start at boot (instead of just manually by doing: /usr/local/etc/rc.d/vdr onestart ) you need to set: vdr_enable=YES too of course. And for vdradmin_am its: vdradmind_enable=YES If you want to start vdr manually in the foreground instead you need to be root (or the vdr user but vdr also drops to the vdr uid itself if started as root), and then run it like: vdr '-Pxineliboutput --local=none --remote=127.1:37890' -Pskinenigmang -Pfemon -Posdpip '-Posdteletext --cache-system=packed --max-cache=128' -Pstreamdev-server '-Plive -i127.1' -Pepgsearch -Pcontrol -Pinfosatepg -Piptv '-Pupnp -i lo0' 4. Of all the video output methods only xineliboutput and streamdev seem to work (and the vdr-live webinterface browser streaming which also uses streamdev), jpulz also has patches for softdevice so I made a port for that too but it only gave me a black screen... streamdev
Re: some vdr intro/installation notes (watch/record/stream tv)
There are a few things I'd like to comment on. On Sat, Mar 26, 2011 at 12:28 PM, Juergen Lock n...@jelal.kn-bremen.de wrote: So what is vdr? It's something like a luxury settop box/pvr on a pc to receive/watch/record/stream digital tv channels with epg (electronic program guide), timers, client/server networking, webinterface etc pp. So if you have a FreeBSD (or Linux, but that's not covered here :) server you can add one or more dvb/atsc tuner(s) connected to a satellite dish, cable tv or just a dvb-t antenna (or receive iptv streams without a tuner if your isp provides those tho I don't know if anyone tested `real' iptv on FreeBSD yet), browse/search epg, set timers for automated or manual recordings, and watch the streams/recordings elsewhere on your lan. Or if you have a FreeBSD desktop you can also connect a tuner there and do it all on one box - or just run a vdr client like vdr-sxfe (installed by the multimedia/vdr-plugin-xineliboutput port) or a client vdr instance using the streamdev-client plugin connected to a (possibly Linux) vdr server elsewhere on your lan. It should be noted that VDR was not designed to be a server/client system. While it's technically possible to use it that way, keep in mind that each client will not have it's own access to OSD, timers, etc. Although server/client systems are widely popular these days, I wouldn't expect this kind of major change to happen to VDR any time soon. When and if it ever does, it's going to take a lot of work. Unfortunately I don't recall VDR's author (Klaus Schmidinger) ever expressing interest in this. Note: vdr 1.7.17 is the development branch so expect bugs! (I mostly used it because the stable branch (1.6) doesn't support dvb-s2 and h264...) There are patches for the latest stable branch (1.6.x) which add support for dvb-s2 and h264. The 1.6.x was considered final a long time ago and hasn't/won't receive any updates. All development is done in the current 1.7.x branch. Although VDR has both a stable and developer branch, users should be aware that the developer branch is easily as stable as the stable branch. It's by far the users preferred branch of choice. Nobody should have any worries about running a developer version. The only time I personally run the stable branch is inbetween the closure of the last developer branch and beginning of the next. In other words, I've always ran the newest version and in all the years of doing this, I can count on one finger how many times there was a stability issue. 1. Before you start installing these ports either mount an extra fs with enough space for the recordings on /video or create a video dir elsewhere where there is space, symlink it to /video and make it writable for the vdr user. (or if you do have one big / then you can create the dir on there too of course, I just disabled the mkdir in the port to avoid inadvertently filling up ppl's small / fs.) Or if you don't like a symlink you can also add your video dir as -v dir to vdr's startup args, see below. You can create the default dirs and using them directly, use symlinks to map the default dirs to dirs elsewhere, remap the defaults by editing Makefile, or simply override the defaults using command line options as you've mentioned. I've set my system up so everything VDR/dvb-related goes into /dvb. This makes it very convenient and easy to maintain and archive. Additionally I make use of symlinks such as /vdr which is always linked to the latest VDR version, /pluginsrc which always takes me to /vdr/PLUGINS/src, and so on. If you're a run-and-forget user then it may not matter much but if you tinker a lot then you might consider a similar setup -- you'll have a much easier time navigating around the dirs. 3. I have rc.d scripts for vdr and vdradmin-am but even if you use those you still need to add plugins and their options similar to this to your /etc/rc.conf: You can automate most of the stuff required to run VDR, and everything else can be put in a .conf somewhere for the stuff that can't. I've found this extremely useful and worth looking into for any level user. 4. Of all the video output methods only xineliboutput and streamdev seem to work (and the vdr-live webinterface browser streaming which also uses streamdev), jpulz also has patches for softdevice so I made a port for that too but it only gave me a black screen... streamdev doesn't have an osd so you probably want xineliboutput at least for the first setup. Users also have the option of using vdr-xine, which is an alternative to xineliboutput. I'm only aware of a few differences between them, none of which have any real significance to me but the vdr-xine author, Reinhard Nissl, is an active developer of xine-lib's vdpau support as well. I've never used xineliboutput myself because of Rnissl's accessibility and status as a xine-lib vdpau contributor. The user bases for both
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 10:11 AM, Baptiste Daroussin b...@freebsd.org wrote: Developpement site: http://git.etoilebsd.net/pkgng/ FYI, we moved to github[1] in order to have a bug tracker, pull request and code review. Also, I recommend to build from the HEAD of the git repository, to not report fixed compilation warnings/bugs. [1]: https://github.com/pkgng/pkgng ___ 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
Re: Updating multiple ports with portmaster
Matthias Andree wrote: ... Is there a way to get portmaster to behave like portupgrade did and only upgrade what needs to be upgraded? This is documented in the portmaster(1) manpage. You can use -a to update all ports that need to be updated. To update a subset of those, you could (1) use -i with -a or a glob (by the way, the * isn't needed with portmaster -- see the portmaster(1) manpage), and respond in the negative to prompts to update or re-install those you wish to exclude; (2) use -x with -a or a glob, to exclude certain ports; or (3) feed portmaster a list of globs that match only those ports that you want to be updated. In your case, for (3), if you only wanted to update those p5-* ports that need to be updated, but not other ports that need to be updated, you could use something like: pkg_version -qos p5- -l '' | xargs portmaster Of course, since some new versions of p5-* ports may depend upon new versions of other, non p5-* ports, updating only the p5-* ports isn't guaranteed to work. portmaster takes care of that, except if there are downstream It tries to take care of it, and usually succeeds for (1) and (3). But not necessarily for (2), if one of the ports that should be updated is excluded. dependencies that stop working with updated ports on your list -- but that's rather rarely observed and usually documented in /usr/ports/UPDATING -- but even then, portmaster -a -i would likely help. Yes, that's something that should also be taken into consideration. Rarely, maybe, but more often than one would like -- and sometimes undocumented. b. ___ 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
Re: some vdr intro/installation notes (watch/record/stream tv)
On Sat, Mar 26, 2011 at 02:55:12PM -0700, VDR User wrote: There are a few things I'd like to comment on. On Sat, Mar 26, 2011 at 12:28 PM, Juergen Lock n...@jelal.kn-bremen.de wrote: So what is vdr? It's something like a luxury settop box/pvr on a pc to receive/watch/record/stream digital tv channels with epg (electronic program guide), timers, client/server networking, webinterface etc pp. So if you have a FreeBSD (or Linux, but that's not covered here :) server you can add one or more dvb/atsc tuner(s) connected to a satellite dish, cable tv or just a dvb-t antenna (or receive iptv streams without a tuner if your isp provides those tho I don't know if anyone tested `real' iptv on FreeBSD yet), browse/search epg, set timers for automated or manual recordings, and watch the streams/recordings elsewhere on your lan. Or if you have a FreeBSD desktop you can also connect a tuner there and do it all on one box - or just run a vdr client like vdr-sxfe (installed by the multimedia/vdr-plugin-xineliboutput port) or a client vdr instance using the streamdev-client plugin connected to a (possibly Linux) vdr server elsewhere on your lan. It should be noted that VDR was not designed to be a server/client system. While it's technically possible to use it that way, keep in mind that each client will not have it's own access to OSD, timers, etc. Although server/client systems are widely popular these days, I wouldn't expect this kind of major change to happen to VDR any time soon. When and if it ever does, it's going to take a lot of work. Unfortunately I don't recall VDR's author (Klaus Schmidinger) ever expressing interest in this. Hm well yeah it could still be better but what is there is not soo bad. Note: vdr 1.7.17 is the development branch so expect bugs! (I mostly used it because the stable branch (1.6) doesn't support dvb-s2 and h264...) There are patches for the latest stable branch (1.6.x) which add support for dvb-s2 and h264. The 1.6.x was considered final a long time ago and hasn't/won't receive any updates. All development is done in the current 1.7.x branch. Although VDR has both a stable and developer branch, users should be aware that the developer branch is easily as stable as the stable branch. It's by far the users preferred branch of choice. Nobody should have any worries about running a developer version. The only time I personally run the stable branch is inbetween the closure of the last developer branch and beginning of the next. In other words, I've always ran the newest version and in all the years of doing this, I can count on one finger how many times there was a stability issue. Well thats even better then. :) (I also had few issues.) 1. Before you start installing these ports either mount an extra fs with enough space for the recordings on /video or create a video dir elsewhere where there is space, symlink it to /video and make it writable for the vdr user. (or if you do have one big / then you can create the dir on there too of course, I just disabled the mkdir in the port to avoid inadvertently filling up ppl's small / fs.) Or if you don't like a symlink you can also add your video dir as -v dir to vdr's startup args, see below. You can create the default dirs and using them directly, use symlinks to map the default dirs to dirs elsewhere, remap the defaults by editing Makefile, or simply override the defaults using command line options as you've mentioned. I've set my system up so everything VDR/dvb-related goes into /dvb. This makes it very convenient and easy to maintain and archive. Additionally I make use of symlinks such as /vdr which is always linked to the latest VDR version, /pluginsrc which always takes me to /vdr/PLUGINS/src, and so on. If you're a run-and-forget user then it may not matter much but if you tinker a lot then you might consider a similar setup -- you'll have a much easier time navigating around the dirs. Well I tried to at least somewhat adhere to hier(7)... 3. I have rc.d scripts for vdr and vdradmin-am but even if you use those you still need to add plugins and their options similar to this to your /etc/rc.conf: You can automate most of the stuff required to run VDR, and everything else can be put in a .conf somewhere for the stuff that can't. I've found this extremely useful and worth looking into for any level user. Well passing plugin args is automated on Linux often but I didn't try to port those scripts, wanted to keep things simple... (editing rc.conf I think is easy enough?) 4. Of all the video output methods only xineliboutput and streamdev seem to work (and the vdr-live webinterface browser streaming which also uses streamdev), jpulz also has patches for softdevice so I made a port for that too but it only gave me a black screen... streamdev doesn't have an osd
Re: some vdr intro/installation notes (watch/record/stream tv)
On Sat, Mar 26, 2011 at 4:44 PM, Juergen Lock n...@jelal.kn-bremen.de wrote: You can automate most of the stuff required to run VDR, and everything else can be put in a .conf somewhere for the stuff that can't. I've found this extremely useful and worth looking into for any level user. Well passing plugin args is automated on Linux often but I didn't try to port those scripts, wanted to keep things simple... (editing rc.conf I think is easy enough?) I'm not a fan of scripts like runvdr to be honest. I opted to just write my own from scratch. I use the bash shell and hadn't considered whether or not freebsd has it available as well. I hope so! With vdr-xine no patching is necessary as long as you using xine-lib-1.2 hg revision 11658 (hash 3501e0a6f75c) or newer. I recommend using this regardless as it contains items necessary for VDR-1.7.17's new truecolor OSD support. So xine-lib 1.2 is recommendable yet? I was so far trying to stick to 1.1.19 release + patches since other FreeBSD ports use libxine too and I know nothing at all about the 1.2 branch and how stable it is... :) Originally vdpau support was being developed against the 1.1 branch but it eventually matured to the point where it was merged into xine-lib-1.2 directly. Since then all development has been against xine-lib.1.2 with no backporting that I'm aware of. When vdpau was merged, I made the switch to the 1.2 branch. There have been a few bumps in the road but those were all resolved and my experience now is that xine-lib-1.2 vdpau is very stable. I'd say it's worth trying and see if you get the same results because it's sure a lot easier then maintaining a bunch of patches. :) Your ion1 should be able to handle temporal, as mine does. Using half temporal shouldn't be necessary. Ok I should check that. Hmm no, a 1080i recording of `Servus TV Hockey night' I did for testing deinterlacing looks `jumpy' with temporal when there is more motion. Maybe things have improved in libxine 1.2? It could be. I know vdpau support was completely re-written from scratch a little while back. There's also another alternative vdpau implementation being developed (also against 1.2) which is already working but looking good so far. IIRC it needs some work and a lot of code clean-up though. - Small bug: if playback of a recording doesn't start try pressing Green. (or F6 with my example remote.conf keyboard mapping.) I've never heard of this bug. Could you elaborate? It mostly happens with short recordings that were already played before... I think. (Tho I also yesterday saw it with vdpau on a longer recording, for the first time.) I tried it here and couldn't reproduce the problem. I wonder if this is related to using xine-lib-1.1 vdpau? Are you aware of any linux users with the problem also? Oh, if you have a link for that... :) I actually don't but I'll attach it to this post. :) Cheers vdr-1.7.17-fix_na_dvbs_ac3.diff Description: Binary data ___ 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
Re: Updating multiple ports with portmaster
On 03/26/2011 10:00, Matthew Seaman wrote:
pkg_version -vIL= | awk '/^p5-/ { print $1 }' | xargs portmaster
That's a good suggestion, but if you want to use that technique, better
would be: portmaster `pkg_version -vIL= | awk '/^p5-/ { print $1 }'` so
that you can take advantage of the internal caching that portmaster does.
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
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
