Re: [Fink-devel] Conflicts/Replaces for obsolete packages
On Dec 4, 2007 9:29 PM, Alexander K. Hansen <[EMAIL PROTECTED]> wrote: > Charles Lepple wrote: > > Hi all, > > > > The latest upstream of gerbv has dropped support for GTK+1, so I > > would like to move to a single package file for gerbv.info and > > gerbv-gtk2.info. > > > > I used to have gerbv conflict and replace gerbv-gtk2 (and vice > > versa) since it didn't seem worth it to have both packages coexist > > (it's small enough to swap out if needed). Now, gerbv-gtk2 is a > > bundle/splitoff that just depends on the main package and > > fink-obsolete-packages. > > > > For some reason, I kept the Replaces: line in the main file so that > > it could overwrite the old gerbv-gtk2 package, but that produces > > some interesting error messages if you upgrade by typing "fink > > install gerbv-gtk2". > > > > Is it reasonable to have the old package be replaced by the unified > > one? Should I just stick to the traditional method of depending on > > fink-obsolete-packages, and letting the user clean up obsolete > > packages manually? > > > > The working .info file is attached. > > > > > One issue to consider is that if the dummy upgrader is a splitoff even > users who are building the package for the first time will install > fink-obsolete-packages, and some find that unnerving. Interesting, I hadn't thought of that side effect (fink-obsolete-packages was already on my system). There is already a gerbv-gtk2.info file in CVS, so I'll just use that for the obsolete part. thanks, -- - Charles Lepple - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] Conflicts/Replaces for obsolete packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles Lepple wrote: > Hi all, > > The latest upstream of gerbv has dropped support for GTK+1, so I > would like to move to a single package file for gerbv.info and > gerbv-gtk2.info. > > I used to have gerbv conflict and replace gerbv-gtk2 (and vice > versa) since it didn't seem worth it to have both packages coexist > (it's small enough to swap out if needed). Now, gerbv-gtk2 is a > bundle/splitoff that just depends on the main package and > fink-obsolete-packages. > > For some reason, I kept the Replaces: line in the main file so that > it could overwrite the old gerbv-gtk2 package, but that produces > some interesting error messages if you upgrade by typing "fink > install gerbv-gtk2". > > Is it reasonable to have the old package be replaced by the unified > one? Should I just stick to the traditional method of depending on > fink-obsolete-packages, and letting the user clean up obsolete > packages manually? > > The working .info file is attached. > > One issue to consider is that if the dummy upgrader is a splitoff even users who are building the package for the first time will install fink-obsolete-packages, and some find that unnerving. For my own obsoleted packages I wound up using a separate .info file for the dummy upgrade package to avoid that. I think you only need to have the placeholders be splitoffs when they're to supplant dependent - -shlibs packages for a main. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHVgzvB8UpO3rKjQ8RAuX9AJ9T78Z2AaHuUTGTMbEzqfla3JKmKQCfT68u QIORIHD+VRzlgOjxwJt6qoM= =4ESl -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
[Fink-devel] Conflicts/Replaces for obsolete packages
Hi all, The latest upstream of gerbv has dropped support for GTK+1, so I would like to move to a single package file for gerbv.info and gerbv-gtk2.info. I used to have gerbv conflict and replace gerbv-gtk2 (and vice versa) since it didn't seem worth it to have both packages coexist (it's small enough to swap out if needed). Now, gerbv-gtk2 is a bundle/splitoff that just depends on the main package and fink-obsolete-packages. For some reason, I kept the Replaces: line in the main file so that it could overwrite the old gerbv-gtk2 package, but that produces some interesting error messages if you upgrade by typing "fink install gerbv-gtk2". Is it reasonable to have the old package be replaced by the unified one? Should I just stick to the traditional method of depending on fink-obsolete-packages, and letting the user clean up obsolete packages manually? The working .info file is attached. -- - Charles Lepple gerbv.info Description: Binary data - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] dlopen symbol not found
On Dec 4, 2007, at 1:07 AM, Daniel Macks wrote: > In particular, > it's supplied by the deprecated_Emboss_str.o file in the > bio-emboss-pm586 build dir ("nm" on that file reports it as "T"). Ahaaa - because I earlier got many warnings for deprecacted files (eg deprecated_Emboss_str.c:3878: warning: 'ajStrTokenCount' is deprecated), I set a flag in the Makefile to not use them. Turns out that the test file still needs them, hence the error :) Not sure if that would have caused my original error - at least this whole discussion revealed that there also was an upstream error. I have committed the updated files for emboss and bio-emboss-pm. thanks again for all the help, - Koen. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] Xerces-C compilation frustration
no help here, but fwiw, on leopard/intel all of the xerces packages build and install: bash-3.2$ fink list -t xerces Information about 6196 packages read in 2 seconds. i xerces-c2.7.0-1002 XML parser in C++ i xerces-c-dev2.7.0-1002 XML parser in C++ i xerces-c-shlibs 2.7.0-1002 XML parser in C++ i xerces-j2.8.0-1 XML parser in Java i xerces-j-docs 2.8.0-1 Documentation for xerces-j bash-3.2$ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] Xerces-C compilation frustration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jürgen Lorenz Simon wrote: > Hi, > > I'm at the end of my rope here. The last week I've been forced to use > fink > excessively. Most packages work fine, but there are certain things > that can > just stop one in its tracks. For instance the compilation problem > with xerces-c. > > Also, I tried to find out, if there was another package I could use > (another xerces version), > but since the package database is down for weeks now, this is also no > option, which leaves > me dead in the water. > > > fink dumpinfo -fallversions xerces-c That actually can return more versions than does the package database, for cases where there are old versions that have left around for compatibility issues, etc. > I'm using OSX 10.4 and my fink is updated. > > > > uilding /sw/src/fink.build/xerces-c-2.7.0-1002/xerces-c-src_2_7_0/lib/ > libxerces-depdom.27.0.dylib > c++ -DMACOSX -dynamiclib -install_name /sw/lib/libxerces-depdom. > 27.dylib -o /sw/src/fink.build/xerces-c-2.7.0-1002/xerces-c- > src_2_7_0/lib/libxerces-depdom.27.0.dylib MACOSX/depdom/AttrImpl.o > MACOSX/depdom/AttrMapImpl.o MACOSX/depdom/AttrNSImpl.o MACOSX/depdom/ > CDATASectionImpl.o MACOSX/depdom/CharacterDataImpl.o MACOSX/depdom/ > ChildNode.o MACOSX/depdom/CommentImpl.o MACOSX/depdom/DOMParser.o > MACOSX/depdom/DOMString.o MACOSX/depdom/DOM_Attr.o MACOSX/depdom/ > DOM_CDATASection.o MACOSX/depdom/DOM_CharacterData.o MACOSX/depdom/ > DOM_Comment.o MACOSX/depdom/DOM_DOMException.o MACOSX/depdom/ > DOM_DOMImplementation.o MACOSX/depdom/DOM_Document.o MACOSX/depdom/ > DOM_DocumentFragment.o MACOSX/depdom/DOM_DocumentType.o MACOSX/depdom/ > DOM_Element.o MACOSX/depdom/DOM_Entity.o MACOSX/depdom/ > DOM_EntityReference.o MACOSX/depdom/DOM_NamedNodeMap.o MACOSX/depdom/ > DOM_Node.o MACOSX/depdom/DOM_NodeFilter.o MACOSX/depdom/ > DOM_NodeIterator.o MACOSX/depdom/DOM_NodeList.o MACOSX/depdom/ > DOM_Notation.o MACOSX/depdom/DOM_ProcessingInstruction.o MACOSX/ > depdom/DOM_Range.o MACOSX/depdom/DOM_RangeException.o MACOSX/depdom/ > DOM_Text.o MACOSX/depdom/DOM_TreeWalker.o MACOSX/depdom/DOM_XMLDecl.o > MACOSX/depdom/DStringPool.o MACOSX/depdom/DeepNodeListImpl.o MACOSX/ > depdom/DocumentFragmentImpl.o MACOSX/depdom/DocumentImpl.o MACOSX/ > depdom/DocumentTypeImpl.o MACOSX/depdom/DomMemDebug.o MACOSX/depdom/ > ElementDefinitionImpl.o MACOSX/depdom/ElementImpl.o MACOSX/depdom/ > ElementNSImpl.o MACOSX/depdom/EntityImpl.o MACOSX/depdom/ > EntityReferenceImpl.o MACOSX/depdom/NamedNodeMapImpl.o MACOSX/depdom/ > NodeIDMap.o MACOSX/depdom/NodeImpl.o MACOSX/depdom/NodeIteratorImpl.o > MACOSX/depdom/NodeListImpl.o MACOSX/depdom/NodeVector.o MACOSX/depdom/ > NotationImpl.o MACOSX/depdom/ParentNode.o MACOSX/depdom/ > ProcessingInstructionImpl.o MACOSX/depdom/RangeImpl.o MACOSX/depdom/ > RefCountedImpl.o MACOSX/depdom/TextImpl.o MACOSX/depdom/ > TreeWalkerImpl.o MACOSX/depdom/XMLDeclImpl.o -framework > CoreServices -lpthread -L/usr/lib -L/sw/src/fink.build/xerces- > c-2.7.0-1002/xerces-c-src_2_7_0/lib -lxerces-c > ld: Undefined symbols: > __ZN11xercesc_2_712XMLException14loadExceptTextENS_10XMLExcepts5CodesE > __ZN11xercesc_2_712XMLExceptionC2EPKcjPNS_13MemoryManagerE > __ZN11xercesc_2_712XMLExceptionC2ERKS0_ > __ZN11xercesc_2_712XMLExceptionD2Ev > __ZN11xercesc_2_76XMLUni37fgArrayIndexOutOfBoundsException_NameE > __ZN11xercesc_2_77XMemorydlEPv > __ZN11xercesc_2_77XMemorydlEPvPNS_13MemoryManagerE > __ZN11xercesc_2_77XMemorynwEmPNS_13MemoryManagerE > __ZTIN11xercesc_2_712XMLExceptionE > __ZN11xercesc_2_718XMLRegisterCleanupC1Ev > __ZN11xercesc_2_710XMLRefInfo9serializeERNS_16XSerializeEngineE > __ZN11xercesc_2_710XMLScanner11loadGrammarEPKcsb > __ZN11xercesc_2_710XMLScanner11loadGrammarEPKtsb > __ZN11xercesc_2_710XMLScanner12scanDocumentEPKc > __ZN11xercesc_2_710XMLScanner12scanDocumentEPKt > __ZN11xercesc_2_710XMLScanner16setParseSettingsEPS0_ > __ZN11xercesc_2_710XMLScanner16setURIStringPoolEPNS_13XMLStringPoolE > __ZN11xercesc_2_710XMLScanner9scanFirstEPKcRNS_13XMLPScanTokenE > __ZN11xercesc_2_710XMLScanner9scanFirstEPKtRNS_13XMLPScanTokenE > __ZN11xercesc_2_710XMLScanner9scanFirstERKNS_11InputSourceERNS_13XMLPSca > nTokenE > __ZN11xercesc_2_710XMLScanner9scanResetERNS_13XMLPScanTokenE > __ZN11xercesc_2_713DTDEntityDecl9serializeERNS_16XSerializeEngineE > __ZN11xercesc_2_713XMLAttDefList9serializeERNS_16XSerializeEngineE > __ZN11xercesc_2_713XMLEntityDeclD2Ev > __ZN11xercesc_2_715ContentSpecNode9serializeERNS_16XSerializeEngineE > __ZN11xercesc_2_715GrammarResolver10getGrammarEPKt > __ZN11xercesc_2_715GrammarResolver18resetCachedGrammarEv > __ZN11xercesc_2_715GrammarResolverC1EPNS_14XMLGrammarPoolEPNS_13MemoryMa > nagerE > __ZN11xercesc_2_715GrammarResolverD1Ev > __ZN11xercesc_2_717SAXParseExceptionC1EPKtS2_S2_llPNS_13MemoryManagerE > __ZN11xercesc_2_717SAXParseExceptionC1ERKS0_ > __ZN11xercesc_2_717SAXParseExceptionD1Ev > __ZN11xercesc_2_718XMLScannerResolver14resolveScannerEPKtPNS_12XMLValida > torEPNS_15Gr
[Fink-devel] Xerces-C compilation frustration
Hi, I'm at the end of my rope here. The last week I've been forced to use fink excessively. Most packages work fine, but there are certain things that can just stop one in its tracks. For instance the compilation problem with xerces-c. Also, I tried to find out, if there was another package I could use (another xerces version), but since the package database is down for weeks now, this is also no option, which leaves me dead in the water. I'm using OSX 10.4 and my fink is updated. uilding /sw/src/fink.build/xerces-c-2.7.0-1002/xerces-c-src_2_7_0/lib/ libxerces-depdom.27.0.dylib c++ -DMACOSX -dynamiclib -install_name /sw/lib/libxerces-depdom. 27.dylib -o /sw/src/fink.build/xerces-c-2.7.0-1002/xerces-c- src_2_7_0/lib/libxerces-depdom.27.0.dylib MACOSX/depdom/AttrImpl.o MACOSX/depdom/AttrMapImpl.o MACOSX/depdom/AttrNSImpl.o MACOSX/depdom/ CDATASectionImpl.o MACOSX/depdom/CharacterDataImpl.o MACOSX/depdom/ ChildNode.o MACOSX/depdom/CommentImpl.o MACOSX/depdom/DOMParser.o MACOSX/depdom/DOMString.o MACOSX/depdom/DOM_Attr.o MACOSX/depdom/ DOM_CDATASection.o MACOSX/depdom/DOM_CharacterData.o MACOSX/depdom/ DOM_Comment.o MACOSX/depdom/DOM_DOMException.o MACOSX/depdom/ DOM_DOMImplementation.o MACOSX/depdom/DOM_Document.o MACOSX/depdom/ DOM_DocumentFragment.o MACOSX/depdom/DOM_DocumentType.o MACOSX/depdom/ DOM_Element.o MACOSX/depdom/DOM_Entity.o MACOSX/depdom/ DOM_EntityReference.o MACOSX/depdom/DOM_NamedNodeMap.o MACOSX/depdom/ DOM_Node.o MACOSX/depdom/DOM_NodeFilter.o MACOSX/depdom/ DOM_NodeIterator.o MACOSX/depdom/DOM_NodeList.o MACOSX/depdom/ DOM_Notation.o MACOSX/depdom/DOM_ProcessingInstruction.o MACOSX/ depdom/DOM_Range.o MACOSX/depdom/DOM_RangeException.o MACOSX/depdom/ DOM_Text.o MACOSX/depdom/DOM_TreeWalker.o MACOSX/depdom/DOM_XMLDecl.o MACOSX/depdom/DStringPool.o MACOSX/depdom/DeepNodeListImpl.o MACOSX/ depdom/DocumentFragmentImpl.o MACOSX/depdom/DocumentImpl.o MACOSX/ depdom/DocumentTypeImpl.o MACOSX/depdom/DomMemDebug.o MACOSX/depdom/ ElementDefinitionImpl.o MACOSX/depdom/ElementImpl.o MACOSX/depdom/ ElementNSImpl.o MACOSX/depdom/EntityImpl.o MACOSX/depdom/ EntityReferenceImpl.o MACOSX/depdom/NamedNodeMapImpl.o MACOSX/depdom/ NodeIDMap.o MACOSX/depdom/NodeImpl.o MACOSX/depdom/NodeIteratorImpl.o MACOSX/depdom/NodeListImpl.o MACOSX/depdom/NodeVector.o MACOSX/depdom/ NotationImpl.o MACOSX/depdom/ParentNode.o MACOSX/depdom/ ProcessingInstructionImpl.o MACOSX/depdom/RangeImpl.o MACOSX/depdom/ RefCountedImpl.o MACOSX/depdom/TextImpl.o MACOSX/depdom/ TreeWalkerImpl.o MACOSX/depdom/XMLDeclImpl.o -framework CoreServices -lpthread -L/usr/lib -L/sw/src/fink.build/xerces- c-2.7.0-1002/xerces-c-src_2_7_0/lib -lxerces-c ld: Undefined symbols: __ZN11xercesc_2_712XMLException14loadExceptTextENS_10XMLExcepts5CodesE __ZN11xercesc_2_712XMLExceptionC2EPKcjPNS_13MemoryManagerE __ZN11xercesc_2_712XMLExceptionC2ERKS0_ __ZN11xercesc_2_712XMLExceptionD2Ev __ZN11xercesc_2_76XMLUni37fgArrayIndexOutOfBoundsException_NameE __ZN11xercesc_2_77XMemorydlEPv __ZN11xercesc_2_77XMemorydlEPvPNS_13MemoryManagerE __ZN11xercesc_2_77XMemorynwEmPNS_13MemoryManagerE __ZTIN11xercesc_2_712XMLExceptionE __ZN11xercesc_2_718XMLRegisterCleanupC1Ev __ZN11xercesc_2_710XMLRefInfo9serializeERNS_16XSerializeEngineE __ZN11xercesc_2_710XMLScanner11loadGrammarEPKcsb __ZN11xercesc_2_710XMLScanner11loadGrammarEPKtsb __ZN11xercesc_2_710XMLScanner12scanDocumentEPKc __ZN11xercesc_2_710XMLScanner12scanDocumentEPKt __ZN11xercesc_2_710XMLScanner16setParseSettingsEPS0_ __ZN11xercesc_2_710XMLScanner16setURIStringPoolEPNS_13XMLStringPoolE __ZN11xercesc_2_710XMLScanner9scanFirstEPKcRNS_13XMLPScanTokenE __ZN11xercesc_2_710XMLScanner9scanFirstEPKtRNS_13XMLPScanTokenE __ZN11xercesc_2_710XMLScanner9scanFirstERKNS_11InputSourceERNS_13XMLPSca nTokenE __ZN11xercesc_2_710XMLScanner9scanResetERNS_13XMLPScanTokenE __ZN11xercesc_2_713DTDEntityDecl9serializeERNS_16XSerializeEngineE __ZN11xercesc_2_713XMLAttDefList9serializeERNS_16XSerializeEngineE __ZN11xercesc_2_713XMLEntityDeclD2Ev __ZN11xercesc_2_715ContentSpecNode9serializeERNS_16XSerializeEngineE __ZN11xercesc_2_715GrammarResolver10getGrammarEPKt __ZN11xercesc_2_715GrammarResolver18resetCachedGrammarEv __ZN11xercesc_2_715GrammarResolverC1EPNS_14XMLGrammarPoolEPNS_13MemoryMa nagerE __ZN11xercesc_2_715GrammarResolverD1Ev __ZN11xercesc_2_717SAXParseExceptionC1EPKtS2_S2_llPNS_13MemoryManagerE __ZN11xercesc_2_717SAXParseExceptionC1ERKS0_ __ZN11xercesc_2_717SAXParseExceptionD1Ev __ZN11xercesc_2_718XMLScannerResolver14resolveScannerEPKtPNS_12XMLValida torEPNS_15GrammarResolverEPNS_13MemoryManagerE __ZN11xercesc_2_718XMLScannerResolver17getDefaultScannerEPNS_12XMLValida torEPNS_15GrammarResolverEPNS_13MemoryManagerE __ZN11xercesc_2_75QName10getRawNameEv __ZN11xercesc_2_76XMLUni10fgIDStringE __ZN11xercesc_2_76XMLUni12fgElemStringE __ZN11xercesc_2_76XMLUni12fgXMLURINameE __ZN11xercesc_2_76XMLUni13fgCDATAStringE __ZN11xercesc_2_76XMLUni13fgFixedStringE __ZN11xercesc_2_76XMLU