Difference between revisions of "Fink:Policy:Trees"
(revise description of ssl linking) |
(→Tree Modularity: make it a one-liner) |
||
Line 29: | Line 29: | ||
An alternative way to test for modularity and find all unsatisfied dependencies is: |
An alternative way to test for modularity and find all unsatisfied dependencies is: |
||
− | <pre>fink --trees=stable,virtual list --format=dotty > |
+ | <pre>fink --trees=stable,virtual list --format=dotty | perl -n -e 'if (/"(.*?)" -> "(.*?)"/) { push @{$need{$2}}, $1} elsif (/"(.*?)" \[/) {$have{$1}++}} END {foreach (sort keys %need) {print "missing $_ for ".join(" ",@{$need{$_}})."\n" unless $have{$_}}'</pre> |
− | perl -n -e 'if (/"(.*?)" -> "(.*?)"/) { push @{$need{$2}}, $1} elsif (/"(.*?)" \[/) {$have{$1}++}} END {foreach (sort keys %need) {print "missing $_ for ".join(" ",@{$need{$_}})."\n" unless $have{$_}}' foo.dot</pre> |
||
Revision as of 19:28, 26 October 2015
Linking Against OpenSSL
If the package currently has to be marked "License: Restrictive" because it links against OpenSSL, there is a workaround. The GPL specifies that it is OK to link against non-GPL software if it is a system-provided library. Since Apple includes OpenSSL as part of the base Mac OS X install, it can be linked against without license issues.
To do so, use the system-openssl-dev package.
Tree Modularity
Any package in the stable tree must have all its (Build)Depends be satisfiable by packages in the stable tree. The idea is that a user could use only the stable tree and still still have a self-contained fink installation with no missing dependent packages.
Prior to July 1, 2010, any package that had a (Build)Depends that can only be satisfied by package(s) in section:crypto was required to itself be in section:crypto. This requirement was dropped when crypto was moved into the main tree.
You can pipe the output of 'fink list' into 'fink rebuild' to see if there are any packages with broken dependencies. The subsets are:
- stable/main
- unstable/main stable/main
(There used to be two more subsets, involving the crypto tree.)
Because some users might only have unstable/main, every package in the stable tree should also appear in the unstable tree, in either the same or a more recent version.
You can use fink's --trees flag instead of having to alter the Trees
line in your fink.conf
file for each subset of the distro, for example:
fink --trees=stable/main list -t | grep -v '\[' | cut -f2 > pkgs
edit pkgs
to remove any known blockers:
libgems-rb*
andrubygems-rb*
(-rb16 and -rb18 cannot be built concurrently)
cat pkgs | xargs fink --trees=stable/main,virtual rebuild
An alternative way to test for modularity and find all unsatisfied dependencies is:
fink --trees=stable,virtual list --format=dotty | perl -n -e 'if (/"(.*?)" -> "(.*?)"/) { push @{$need{$2}}, $1} elsif (/"(.*?)" \[/) {$have{$1}++}} END {foreach (sort keys %need) {print "missing $_ for ".join(" ",@{$need{$_}})."\n" unless $have{$_}}'