Re: [Fink-devel] Confusion with rapidsvn linked libs

Trevor Harmon wrote: > On Jul 7, 2009, at 2:40 PM, Alexander Hansen wrote: > >> The Files: will have the file names, of course: >> >> Files: << >>lib/libsvncpp.2.0.0.dylib >>lib/libsvncpp.2.dylib >> << > > It seems only the libsvncpp.2.dylib is generated. Do I need to add an > InstallScript

Re: [Fink-devel] Confusion with rapidsvn linked libs

On Jul 7, 2009, at 10:44 PM, Alexander Hansen wrote: > You can leave it out. Thanks for your help! I've uploaded the package to the tracker: https://sourceforge.net/tracker/?func=detail&aid=2818340&group_id=17203&atid=414256 Trevor -

Re: [Fink-devel] Confusion with rapidsvn linked libs

On Jul 7, 2009, at 2:40 PM, Alexander Hansen wrote: > The Files: will have the file names, of course: > > Files: << >lib/libsvncpp.2.0.0.dylib >lib/libsvncpp.2.dylib > << It seems only the libsvncpp.2.dylib is generated. Do I need to add an InstallScript in the splitoff to softlink the

Re: [Fink-devel] Confusion with rapidsvn linked libs

Trevor Harmon wrote: > On Jul 7, 2009, at 12:27 PM, Alexander Hansen wrote: > >> This should be all right. > > Okay, so how do I map these version numbers (2 and 3.0.0) into the > .info file? For example, here are the old portions of the .info that > need updating: > > ... > Package: svncpp0-de

[Fink-devel] Tracker hiatus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm wrapping up my month in Norway, and I need to spend time analyzing my data and coming up with a summary of what I've done while here. I'm therefore not going to be touching tracker submissions until I get back home. - -- Alexander Hansen Fink User

Re: [Fink-devel] Confusion with rapidsvn linked libs

On Jul 7, 2009, at 12:27 PM, Alexander Hansen wrote: > This should be all right. Okay, so how do I map these version numbers (2 and 3.0.0) into the .info file? For example, here are the old portions of the .info that need updating: ... Package: svncpp0-dev Depends: svncpp0-shlibs (=

Re: [Fink-devel] openmpi-1.3.2-1003 test packaging

On 07/07/2009, at 10:21, Jack Howarth wrote: > Try the revised info file I uploaded to fink tracking. > If this doesn't solve the problem, one of the core fink > developers will have to look at it to explain why fink > shows a validation (but not a packaging error). Hello, Jack. The new package

Re: [Fink-devel] Confusion with rapidsvn linked libs

Trevor Harmon wrote: > Hi, > > I'm the maintainer of the rapidsvn package, and I'm trying to update > it to the latest upstream version, but I'm stuck. The main problem > seems to be a change in the versioning of the svncpp shared libraries > that are associated with the package. The old upstream r

[Fink-devel] Confusion with rapidsvn linked libs

Hi, I'm the maintainer of the rapidsvn package, and I'm trying to update it to the latest upstream version, but I'm stuck. The main problem seems to be a change in the versioning of the svncpp shared libraries that are associated with the package. The old upstream release apparently had n

Re: [Fink-devel] openmpi-1.3.2-1003 test packaging

Monipol, Try the revised info file I uploaded to fink tracking. If this doesn't solve the problem, one of the core fink developers will have to look at it to explain why fink shows a validation (but not a packaging error). Jack On Tue, Jul 07, 2009 at 07:35:42AM -0300, monipo

Re: [Fink-devel] Problem of Addding Header in Patch file

On Tue, Jul 7, 2009 at 2:54 PM, tarun gulyani wrote: > Hi All, > > Please tell me how to add header in patch file. Actually i am creating patch > using "diff -Nur install.sh install_1.sh > gnowsys.patch". > > It giving error, when i am checking patch using "patch -p1 < > gnowsys.patch". > > > Error

Re: [Fink-devel] Adding Header in Patch file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/7/09 9:19 AM, Sandeep Bhaskar wrote: > Please tell me how to add header in patch file. Actually I tried > creating patch using "diff -Nur install.sh install_1.sh > gnowsys.patch". Charles already answered your question. Please, on a public disc

[Fink-devel] Adding Header in Patch file

Hi All, Please tell me how to add header in patch file. Actually I tried creating patch using "diff -Nur install.sh install_1.sh > gnowsys.patch". Its giving error, when i am checking patch using "patch -p1 < gnowsys.patch". Error is : patch -p1 < gnowsys.patch missing header for unified diff

Re: [Fink-devel] Problem of Addding Header in Patch file

On Tue, Jul 7, 2009 at 8:54 AM, tarun gulyani wrote: > Hi All, > > Please tell me how to add header in patch file. Actually i am creating patch > using "diff -Nur install.sh install_1.sh > gnowsys.patch". Run "cd .." first, and add the directory name. Also, I think the 2nd filename needs to match

[Fink-devel] Problem of Addding Header in Patch file

Hi All, Please tell me how to add header in patch file. Actually i am creating patch using "diff -Nur install.sh install_1.sh > gnowsys.patch". It giving error, when i am checking patch using "patch -p1 < gnowsys.patch". Error is : patch -p1 < gnowsys.patch missing header for unified diff at l

[Fink-devel] Problem of Addding Header in Patch file

Hi All, Please tell me how to add header in patch file. Actually i am creating patch using "diff -Nur install.sh install_1.sh > gnowsys.patch". It giving error, when i am checking patch using "patch -p1 < gnowsys.patch". Error is : patch -p1 < gnowsys.patch missing header for unified diff at l

[Fink-devel] Problem of Addding Header in Patch file

Hi All, Please tell me how to add header in patch file. Actually i am creating patch using "diff -Nur install.sh install_1.sh > gnowsys.patch". It giving error, when i am checking patch using "patch -p1 < gnowsys.patch". Error is : patch -p1 < gnowsys.patch missing header for unified diff at l

Re: [Fink-devel] openmpi-1.3.2-1003 test packaging

On 06/07/2009, at 21:56, Jack Howarth wrote: > I have posted test packaging for openmpi-1.3.2-1003... > > https://sourceforge.net/tracker/?func=detail&aid=2817726&group_id=17203&atid=414256 > > which should solve the problems with case-sensitive filesystems. The > approach > I adopted was to use.