I'm cc'ing Fink-devel on this one to fill in any gaps in my knowledge. On 8/25/06, Robert Stroud <[EMAIL PROTECTED]> wrote: > Alexander, > > Clytie apparently needs gettext-0.15 but fink and darwin ports only > have gettext-0.14 for some reason. However, gettext-0.15 seems to > build fine on my machine, so how hard would it be to upgrade the > existing gettext package descriptor used by fink to version 0.15? Is > fink leveraging some existing package system, or does it use its own > package descriptors? >
Fink uses Debian's tools, and has its own descriptors as well for build-time. The primary issue with gettext is that it's an essential package, so any update to it has nontrivial consequences. This is why it took forever to update it from 0.10.40 to 0.14.5 in the stable tree. > What happens if there's stuff installed that depends on gettext? Will > it depend on a particular version of gettext, and will it get rebuilt > if gettext is upgraded? Versioned dependencies are set in the descriptions of an individual package. If A depends on B a rebuild of A isn't forced on an update of B unless it is determined that A does in fact require a rebuild when B is updated, and is therefore updated itself. There are packages that have versioned dependencies on the various gettext splitoffs, but I think those are primarily to ensure that the -tools and -bin packages are for 0.14.5 and not the deprecated 0.10.40. Similarly, how do you determine what gettext > itself depends on In general it's good to go with what the existing packages use: $ fink dumpinfo -fbuilddepends -fdepends libgettext3-shlibs Information about 6082 packages read in 3 seconds. builddepends: libiconv-dev, fink (>= 0.24.12) depends: libiconv, libiconv-bin, base-files , and whether it requires a particular version or > not? Updating gettext forces a version update for fink, but there's no other versioned dependency listed. Does fink distinguish between major and minor version numbers, > for example, where a change to a major version number implies a > change to the API that requires re-compilation of any packages that > depend on that API, or are version numbers not used in this kind of way? > Fink generally uses the upstream version numbers (major+minor). What changes correspond to minor version number increments and what changes correspond to major version bumps are up to them to decide. We rely on the package maintainers and users to find out if there are changes in the API that force a rebuild of anything. > Thanks, > > Robert > -- Alexander K. Hansen Fink Documenter (still) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
