Re: [Fink-devel] Re: fink/perlmod/Fink PkgVersion.pm,1.351,1.352 ChangeLog,1.842,1.843
Just to clarify this a little, only comment out the depends and use 'fink build' for testing, make sure you don't commit the pkg with the depends commented, they are still needed for install and run time. This is just to test that all pkgs can build without the depends line. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 4-Feb-05, at 6:28 PM, TheSin wrote: all pkgs such be able fink build foo with out the depends line so comment it out and add what is needed to builddep line. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] PatchScript problem
I've been trying to make a package for aee, and I've run into the
following problem. As stated in the packaging manual, I ran the
following diff command and got a pretty standard patch file. I needed
to make the patch because the path to the help.ae file is hard coded in
the source file.
diff -uraN aee-2.2.3.old aee-2.2.3.new aee.patch
more aee.patch
diff -uraN aee-2.2.3.old/help.c aee-2.2.3.new/help.c
--- aee-2.2.3.old/help.cSun Jan 31 23:28:23 1999
+++ aee-2.2.3.new/help.cThu Feb 3 21:44:53 2005
@@ -11,7 +11,7 @@
#include aee.h
char *help_file_list[4] = {
- /usr/local/aee/help.ae,
+ @PREFIX@/share/doc/aee/help.ae,
/usr/local/lib/help.ae,
~/.help.ae,
help.ae
Now, In my aee.info file, I've got the following line.
PatchScript: sed 's|@PREFIX@|%p|g' %a/%n.patch | patch -p1
Unfortunately, when I try to build the package, I get an error like
this.
aee-2.2.3/genstr
aee-2.2.3/aee.i18n.guide
aee-2.2.3/aee.msg
aee-2.2.3/keypad
aee-2.2.3/aee.1.ps
aee-2.2.3/install-sh
aee-2.2.3/catalog.aee
aee-2.2.3/Changes
sed 's|@PREFIX@|/min|g' /min/fink/dists/local/main/finkinfo/aee.patch
| patch -p1
patching file help.c
Hunk #1 FAILED at 11.
1 out of 1 hunk FAILED -- saving rejects to file help.c.rej
### execution of sed failed, exit code 1
Failed: patching aee-2.2.3-1 failed
I'm pretty sure the error is occurring due to the fact the @PREFIX@ is
within double quotes. I did some experiments, and anytime @PREFIX@ is
placed within double quotes, the patch fails, but anytime it is out of
quotes, the patch is successful. Based on the patch reject file, it
looks like sed is correctly substituting @PREFIX@ with %p, but the
patch command doesn't like the double quotes, or maybe it's a
combination of the commands screwing up. I don't really know.
more help.c.rej
***
*** 11,17
#include aee.h
char *help_file_list[4] = {
-/usr/local/aee/help.ae,
/usr/local/lib/help.ae,
~/.help.ae,
help.ae
--- 11,17
#include aee.h
char *help_file_list[4] = {
+/sw/share/doc/aee/help.ae,
/usr/local/lib/help.ae,
~/.help.ae,
help.ae
So, does anyone know how I can use the patch command to get around this
problem? Or should I just use a series of some other commands to edit
the file prior to compilation?
Jason Park
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Proposed Policy Change for all Maintainers IMPORTANT
With the upcoming shlibs change, the packaging engine needs to be
changed a little and this will break many packages.
first let me explain the shlibs change. Basically fink will beable to
automatically insert all share library deps to the Depends line by
using Depends: {SHLIB_DEPS}, curl | curl-ssl. This is an example and I
added curl | curl-ssl to show that we will still need to add runtime
depends by hand, but now dylib pkgs.
Now currently fink treats Depends and builddepends in the pretty much
the same manor. In the new layout Depends will be Install/Run tim
depends, so not needed to build a package. And since in the new policy
all -dev pkgs will be required to depend on there own -shlibs, we can
rest assured that the -shlibs will be present at build time so no need
to list them in the BuildDepends, except if a -dev isn't currently
following that policy. But there are only a few that aren't at this
point so that won't be a big change.
Anyhow, any maintainer wishing to help us out and help speed this new
great tool up for us, please follow this next set of instructions to
fix your pkgs:
all pkgs such be able fink build foo with out the depends line so
comment it out and add what is needed to builddep line. This is to test
build only, so use fink build to test this and not install. Also
please don't commit it like this. Again this is only to test that the
pkg will build sans the Depends line. Install and Run time deps are
still required at this point and that includes the -shlibs pkgs so
don't start removing those yet.
Also we NEED and I can't stress this enough, need proper shlibs fields.
This will are receive a little more documentation I hope and much more
clarification in the policy and packaging section of our website.
The format is as such
Shlibs:
%p/lib/libfoo.5.dylib 4.0.0 %n (= 4.0-1)
1) installed lib name of the major versioned lib, that means the actual
dylib not the one of the symlinks
2) the compat version of the lib, you can get this by running otool -L
on 1)
3) the lowest version of the pkg that has this lib, should almost
always be %n and a -1 revision of when the compat version of this lib
first made it into a fink pkg, This value shouldn't change until the
next time the compat version on that lib changes.
Also contrary to some pkgs and what we may have stated before please do
NOT use
foo-shlibs (= 1.0-1) | foo-ssl-shlibs (= 1.0-1). We may allow it for
x11 and nox variants but for now please only one pkgname and version.
The more Maintainers do the faster we won't need to worry about Depends
anymore :D
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Proposed Policy Change for all Maintainers IMPORTANT
Le 5 févr. 2005, à 17:01, TheSin a écrit : Anyhow, any maintainer wishing to help us out and help speed this new great tool up for us, please follow this next set of instructions to fix your pkgs: all pkgs such be able fink build foo with out the depends line so comment it out and add what is needed to builddep line. This is to test build only, so use fink build to test this and not install. Also please don't commit it like this. Again this is only to test that the pkg will build sans the Depends line. Install and Run time deps are still required at this point and that includes the -shlibs pkgs so don't start removing those yet. I'll guess you want a report of what builds without changes, what needs changes, and so on. So, under which form and where should it be sent? Also contrary to some pkgs and what we may have stated before please do NOT use foo-shlibs (= 1.0-1) | foo-ssl-shlibs (= 1.0-1). Then what to do with the packages which lists such variations as Depends or BuildDepends? What to do when the variations are different from a branch to another, or from a tree to another one? Michèle http://micmacfr.homeunix.org PGP.sig Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
Re: [Fink-devel] Proposed Policy Change for all Maintainers IMPORTANT
Please make the changes that need be made to builddeps and shlibs fields and committed them to cvs. None of these changes will break pkgs in fink current state. Fink will only break in the next state if these changes have not been made. As for variation. At this point will no longer be interchangeable. This may only be temporary. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 5-Feb-05, at 9:26 AM, Michèle Garoche wrote: Le 5 févr. 2005, à 17:01, TheSin a écrit : Anyhow, any maintainer wishing to help us out and help speed this new great tool up for us, please follow this next set of instructions to fix your pkgs: all pkgs such be able fink build foo with out the depends line so comment it out and add what is needed to builddep line. This is to test build only, so use fink build to test this and not install. Also please don't commit it like this. Again this is only to test that the pkg will build sans the Depends line. Install and Run time deps are still required at this point and that includes the -shlibs pkgs so don't start removing those yet. I'll guess you want a report of what builds without changes, what needs changes, and so on. So, under which form and where should it be sent? Also contrary to some pkgs and what we may have stated before please do NOT use foo-shlibs (= 1.0-1) | foo-ssl-shlibs (= 1.0-1). Then what to do with the packages which lists such variations as Depends or BuildDepends? What to do when the variations are different from a branch to another, or from a tree to another one? Michèle http://micmacfr.homeunix.org --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Proposed Policy Change for all Maintainers IMPORTANT
Le 5 févr. 2005, à 17:41, TheSin a écrit : As for variation. At this point will no longer be interchangeable. This may only be temporary. OK, but how to treat them? Is this true only for -shlibs, or also for -dev or any other imaginable splitoff? For example in glade2, there are a choice between pango1-dev and pango1-xft2-dev, gnome-vf2-ssl-dev and gnome-vf2-ssl and same on shlibs (but pango1-shlibs), all versioned. How many packages should I make: 4 packages or 1 package with 4 variants? As those: pango1, gnome-vfs2 pango1-xft2, gnome-vfs2 pango1, gnome-vfs2-ssl pango1-xft2, gnome-vfs2 Michèle http://micmacfr.homeunix.org PGP.sig Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
Re: [Fink-devel] Proposed Policy Change for all Maintainers IMPORTANT
BuildDepends: and Depends can still have | fields like pango1-dev | pango1-xft2-dev it's only the Shlibs fields for now that we ask only have one pkg name. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 5-Feb-05, at 10:59 AM, Michèle Garoche wrote: Le 5 févr. 2005, à 17:41, TheSin a écrit : As for variation. At this point will no longer be interchangeable. This may only be temporary. OK, but how to treat them? Is this true only for -shlibs, or also for -dev or any other imaginable splitoff? For example in glade2, there are a choice between pango1-dev and pango1-xft2-dev, gnome-vf2-ssl-dev and gnome-vf2-ssl and same on shlibs (but pango1-shlibs), all versioned. How many packages should I make: 4 packages or 1 package with 4 variants? As those: pango1, gnome-vfs2 pango1-xft2, gnome-vfs2 pango1, gnome-vfs2-ssl pango1-xft2, gnome-vfs2 Michèle http://micmacfr.homeunix.org --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: fink/perlmod/Fink PkgVersion.pm,1.351,1.352 ChangeLog,1.842,1.843
Why not make 'fink build' ignore the depends line completely in all cases? -Ben On Feb 5, 2005, at 7:30 AM, TheSin wrote: Just to clarify this a little, only comment out the depends and use 'fink build' for testing, make sure you don't commit the pkg with the depends commented, they are still needed for install and run time. This is just to test that all pkgs can build without the depends line. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 4-Feb-05, at 6:28 PM, TheSin wrote: all pkgs such be able fink build foo with out the depends line so comment it out and add what is needed to builddep line. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: fink/perlmod/Fink PkgVersion.pm,1.351,1.352 ChangeLog,1.842,1.843
in the new engine it will, but we are trying to prep everyone before we break alot of pkgs. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 5-Feb-05, at 12:02 PM, Ben Hines wrote: Why not make 'fink build' ignore the depends line completely in all cases? -Ben On Feb 5, 2005, at 7:30 AM, TheSin wrote: Just to clarify this a little, only comment out the depends and use 'fink build' for testing, make sure you don't commit the pkg with the depends commented, they are still needed for install and run time. This is just to test that all pkgs can build without the depends line. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 4-Feb-05, at 6:28 PM, TheSin wrote: all pkgs such be able fink build foo with out the depends line so comment it out and add what is needed to builddep line. --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: [Planner Dev] Success! - Planner on Darwin/FreeBSD/OSX
Patrick: A month ago I tried to compile planner on my Mac. I began to realize that I am in way over my head. Today I tried again and found your posting on gmane.os.apple.fink.beginners. I had already done the cvs update from :pserver:[EMAIL PROTECTED]:/cvs/gnome (the cvs in your message did not work for me.) Apparently I had already updated my libtool and based on your advice, I updated gettext. When I ran autogen.sh I got some warnings like: Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /sw/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. And the last error it displayed was: config.status: error: cannot find input file: tests/Makefile.in Sure enough, the tests directory is empty. This makes me think that maybe I was using the wrong CVS. But this is the one that Richard Hult at imendio pointed me to. In summary, thanks to your posting, I am much farther than I have been. But I don't know what to do next. I am just beginning to use fink and open source code and I definitely don't understand the .m4 files and how CVS works and what autogen does. If I am almost there, I would ask you to help me. But it may be that there is another 20 hours to get a compile. I just don't know. Would you be willing to help a fellow Dallas person figure this out. Fred Leason P.A.A. wrote: Excellent! Thanks Richard all at imendio for your help, Planner works wonderfully. To help others, here's how I installed Planner on my Powerbook G5, OSX/FreeBSD/Darwin (some easy parts, some tricky parts): 0. Open a new shell/Terminal window. , make sure you are root by typing sudo -s and entering your password 1. Download install the latest libraries (I used Fink -- best way I found on a Mac). This could take a couple of days. 2-3. The latest version of gettext I had to install manually in /usr/local/* for the make to work (for newbies just download it from gnu.org, become root, cd to the gettext directory, type ./configure ; make ; make install 4. Now set the environment as follows: type: setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/sw/lib/pkgconfig ; setenv ACLOCAL_PATH /usr/local/share/aclocal:/sw/share/aclocal ; setenv CVSROOT :pserver:[EMAIL PROTECTED]:/cvs/gnome 5. type cd ~ ; cvs login , press return when asked for a password 6. type cvs co planner 7. type cd planner 9. next tricky part: try typing ./autogen.sh --enable-python=no , if it works, great, if you get a libtool requirement not met then you will need to install the latest version of libtool but first make a backup copy of your current /usr/bin/libtool. After running autogen as above then copy the backup back to /usr/bin/libtool, before typing make, otherwise strange errors happen. 10. type make, if you get an error in the file mrp-parser.c, edit the file and change the gsize above the line on which the error occurs to gint (see Richard's post). 11. type make ; make install , should work fine. make sure X or X11 is running and type /usr/local/bin/planner , and let the good work begin :) For those using fink I'm now working to make a planer package for fink (if someone could do it faster than I that would be great :). Cheers, Patrick Alessandra Assoc. Intl. Dallas * Ft. Worth, Texas U.S.A. (214) 335-0278 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
