Re: Glade3, anyone using/interested in a port?
On Tue, Nov 11, 2008 at 6:07 PM, Jasper Lievisse Adriaanse <[EMAIL PROTECTED]> wrote: > On Mon, Nov 10, 2008 at 12:01:48PM -0500, Jason Beaudoin wrote: >> Re Jasper's additions/cleanup: >> >> > DESCR should be in pkg/ and not in the top level directory. >> >> right, my mistake >> >> > further, i've cleaned up the port a fair bit, and the attached version >> > is what i intend to commit. >> >> great! I have a couple questions/comments, in an attempt at better >> understanding the process. I'd like to continue finding ways to >> contribute, I hope you don't mind my inquisitive nature here :) >> >> > some things i've changed: >> > - updated the port to the latest version >> >> I used the 3.4 series as I understand that the 3.5 (odd) series is the >> unstable track in glade's development: >> http://glade.gnome.org/todo.html >> >> It was also my understanding that, when given the opportunity, using >> the stable release was OpenBSD port's preferred route. > yep, but 3.5 is considered mature enough. > >> > - added missing dependencies (gnome-doc-utils, desktop-file-utils, yelp) >> >> is the dependency for desktop-file-utils pulled in with: DESKTOP_FILES >> = Yes ? > indeed, please see x11/gnome/gnome.port.mk > >> > - added missing PLIST goo (@exec/@unexec) >> >> are you referring to the last few lines of the PLIST file? I'm >> perplexed how I missed this, is there somewhere in the documentation >> that discusses this? > those lines indeed, and it's not fully documented (shame on me). > >> > - start the shared library version at 0.0 >> >> is the convention that the first number is openbsd's (internal) >> sharelib version, and the version given within the comment is external >> to the project, glade in this case? > the "convention" for new libraries is to start at 0.0, no matter the > version of the upstream project. later bumps go according to the rules > layed out in the docs. > >> > - actually make use of gnome.port.mk >> >> I missed details about this, how is this done? > coming soon to a port-modules(5) on a mirror near you! > (for now, just use other ports as a reference.) > >> > - no need for the AUTO*_VERSION variables >> > - add a missing configure argument (we take care of this with @exec in >> > PLIST) >> >> this confuses me.. >> >> scrollkeeper is noted as build/run dependencies, though there is the >> --disable-scrollkeeper configure argument, and calls to exec in the >> PLIST. if you feel up to the task and have time to explain, I'm >> curious how this all works and what I'm missing. > the configure argument (--disable-scrollkeeper) is to make sure the > build process doesn't try to build the scrollkeeper catalog during > install. as this will generate a whole bunch of files into /var (, which > will also trip systrace). > it's just easier to execute the command ourselves at the end of the > installation/removal (@exec/@unexec) and be able to control it. thanks for all the explanations :) cheers! ~Jason
Re: Glade3, anyone using/interested in a port?
On 2008/11/12 00:07, Jasper Lievisse Adriaanse wrote: > > > - start the shared library version at 0.0 > > > > is the convention that the first number is openbsd's (internal) > > sharelib version, and the version given within the comment is external > > to the project, glade in this case? > the "convention" for new libraries is to start at 0.0, no matter the > version of the upstream project. later bumps go according to the rules > layed out in the docs. as well as convention, setting it to something other than upstream's default version is also a useful test to make sure we can actually control the version numbers. sometimes we must bump these across a wide range of ports for some reason (last example: libc/libm/math.h changes), and the last thing you want when sweeping the tree for that sort of update is a port where this can't be controlled. with libtool-based ports this is usually ok, but you run into all sorts in the tree...
Re: Glade3, anyone using/interested in a port?
On Mon, Nov 10, 2008 at 12:01:48PM -0500, Jason Beaudoin wrote: > Re Jasper's additions/cleanup: > > > DESCR should be in pkg/ and not in the top level directory. > > right, my mistake > > > further, i've cleaned up the port a fair bit, and the attached version > > is what i intend to commit. > > great! I have a couple questions/comments, in an attempt at better > understanding the process. I'd like to continue finding ways to > contribute, I hope you don't mind my inquisitive nature here :) > > > some things i've changed: > > - updated the port to the latest version > > I used the 3.4 series as I understand that the 3.5 (odd) series is the > unstable track in glade's development: > http://glade.gnome.org/todo.html > > It was also my understanding that, when given the opportunity, using > the stable release was OpenBSD port's preferred route. yep, but 3.5 is considered mature enough. > > - added missing dependencies (gnome-doc-utils, desktop-file-utils, yelp) > > is the dependency for desktop-file-utils pulled in with: DESKTOP_FILES > = Yes ? indeed, please see x11/gnome/gnome.port.mk > > - added missing PLIST goo (@exec/@unexec) > > are you referring to the last few lines of the PLIST file? I'm > perplexed how I missed this, is there somewhere in the documentation > that discusses this? those lines indeed, and it's not fully documented (shame on me). > > - start the shared library version at 0.0 > > is the convention that the first number is openbsd's (internal) > sharelib version, and the version given within the comment is external > to the project, glade in this case? the "convention" for new libraries is to start at 0.0, no matter the version of the upstream project. later bumps go according to the rules layed out in the docs. > > - actually make use of gnome.port.mk > > I missed details about this, how is this done? coming soon to a port-modules(5) on a mirror near you! (for now, just use other ports as a reference.) > > - no need for the AUTO*_VERSION variables > > - add a missing configure argument (we take care of this with @exec in > > PLIST) > > this confuses me.. > > scrollkeeper is noted as build/run dependencies, though there is the > --disable-scrollkeeper configure argument, and calls to exec in the > PLIST. if you feel up to the task and have time to explain, I'm > curious how this all works and what I'm missing. the configure argument (--disable-scrollkeeper) is to make sure the build process doesn't try to build the scrollkeeper catalog during install. as this will generate a whole bunch of files into /var (, which will also trip systrace). it's just easier to execute the command ourselves at the end of the installation/removal (@exec/@unexec) and be able to control it. > > - and some more minor cleaning. > > thanks! I ran though the make steps to build and test-run the package, > all went well. > > > comments/oks? > > > > cheers, > > jasper cheers, jasper > > -- > > "Intelligence should guide our actions, but in harmony with the > > texture of the situation at hand" > >-- Francisco Varela > > > > Regards, > ~Jason > -- "Intelligence should guide our actions, but in harmony with the texture of the situation at hand" -- Francisco Varela
Re: Glade3, anyone using/interested in a port?
Re Jasper's additions/cleanup: > DESCR should be in pkg/ and not in the top level directory. right, my mistake > further, i've cleaned up the port a fair bit, and the attached version > is what i intend to commit. great! I have a couple questions/comments, in an attempt at better understanding the process. I'd like to continue finding ways to contribute, I hope you don't mind my inquisitive nature here :) > some things i've changed: > - updated the port to the latest version I used the 3.4 series as I understand that the 3.5 (odd) series is the unstable track in glade's development: http://glade.gnome.org/todo.html It was also my understanding that, when given the opportunity, using the stable release was OpenBSD port's preferred route. > - added missing dependencies (gnome-doc-utils, desktop-file-utils, yelp) is the dependency for desktop-file-utils pulled in with: DESKTOP_FILES = Yes ? > - added missing PLIST goo (@exec/@unexec) are you referring to the last few lines of the PLIST file? I'm perplexed how I missed this, is there somewhere in the documentation that discusses this? > - start the shared library version at 0.0 is the convention that the first number is openbsd's (internal) sharelib version, and the version given within the comment is external to the project, glade in this case? > - actually make use of gnome.port.mk I missed details about this, how is this done? > - no need for the AUTO*_VERSION variables > - add a missing configure argument (we take care of this with @exec in > PLIST) this confuses me.. scrollkeeper is noted as build/run dependencies, though there is the --disable-scrollkeeper configure argument, and calls to exec in the PLIST. if you feel up to the task and have time to explain, I'm curious how this all works and what I'm missing. > - and some more minor cleaning. thanks! I ran though the make steps to build and test-run the package, all went well. > comments/oks? > > cheers, > jasper > > -- > "Intelligence should guide our actions, but in harmony with the > texture of the situation at hand" >-- Francisco Varela > Regards, ~Jason
Re: Glade3, anyone using/interested in a port?
hi,
On Sun, Nov 09, 2008 at 10:17:24AM -0500, Jason Beaudoin wrote:
> good morning!
>
>
> an update, some progress, and a request for help:
> - I've attached my port-in-progress, along with some text files that
> I've referenced/used in figuring this out (found under the "ref"
> directory), and the Makefile is at the end of this email.
> - all of the resources I've been pointed towards or found myself
> (openbsd papers, the ports developer documentation, etc) have been
> tremendously helpful, answering all of my questions thus far, the only
> difficulty being dependency resolution.
> - to resolve glade's dependencies, I have used several references,
> and here is what I have so far:
> - glade's own documentation mentions libxml2 and libglade as
> runtime dependencies
> - netbsd's glade3 port has a few "buildlinks" mainly: gtk2,
> libxml2, hicolor-icon-theme, desktop-file-utils, libbonobui, and
> libgnomeui
> - the port-in-progress Jasper provided, also notes
> textproc/scrollkeeper as a build/run-time dependency
>
> - I don't really have a specific problem right now, but I know that
> my Makefile isn't quite working correctly, which I believe stems from
> having the correct dependencies (but I'm not sure).
>
> Current state:
> - I captured the contents of "libs.txt" during a run of make build.
> This helps to show what the configure script found, stuck in glade's
> Makefile, and is now set to be built during make build, but I also
> expect that this helps determine the WANTLIB list.. is this a valid
> assumption?
> - I believe "make configure" works fine (output is included:
> "make_configure.log")
> - "make build" *seems* to work, but I'm skeptical because of the
> issues that arise later, and because I still have the MODULES lines
> commented out (the make build output is included as well:
> "make_build.log"). I also don't really trust all of the DEPENDS lines
> being complete.
> - I have commented out the MODULES line because when it is present, I
> get a lot of the following when running make build (as well as some
> stuff about line 54):
>
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: Missing
> dependency operator
> "/usr/ports/infrastructure/mk/modules.port.mk", line 42: Could not
> find /usr/ports/infrastructure/mk/\ .port.mk
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: warning:
> Missing closing parenthesis for exists()
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: Malformed
> conditional (exists(${PORTSDIR}/infrastructure/mk/\ .port.mk))
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: Missing
> dependency operator
> "/usr/ports/infrastructure/mk/modules.port.mk", line 42: Could not
> find /usr/ports/infrastructure/mk/\ .port.mk
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: warning:
> Missing closing parenthesis for exists()
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: Malformed
> conditional (exists(${PORTSDIR}/infrastructure/mk/\ .port.mk))
> "/usr/ports/infrastructure/mk/modules.port.mk", line 41: Missing
> dependency operator
> "/usr/ports/infrastructure/mk/modules.port.mk", line 42: Could not
> find /usr/ports/infrastructure/mk/\ .port.mk
>
>
> - I am currently a little confused by the output of the depends check
> with "make port-lib-depends-check." The output can be seen in
> ref/make_port-lib-depends-check.log. What I've determined is this:
> - It appears WANTLIBS has entries glade3 doens't need, I'm
> guessing this from the "Bogus WANTLIB" lines in the output. I simply
> copy/pasted the WANTLIB line from the port-in-progress Jasper
> provided, as I'm not sure how to determine these with accuracy.
> - there are a few other libraries needed, as shown by: "WANTLIB
> += Xcomposite Xdamage iconv intl pcre pixman-1"
>
> am I understanding this output correctly?
>
>
> - make package doesn't work, showing that I've screwed up further back
> along the line:
>
> # make package
> ===> Looking for glade3-3.4.5.tgz in $PKG_PATH - not found
> *** Error code 1
>
> Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
> 1416 of /usr/ports/infrastructure/mk/bsd.port.mk).
> `/usr/obj/ports//glade3-3.4.5/fake-i386/.fake_done' is up to date.
> ===> Building package for glade3-3.4.5
> Create /usr/ports/packages/i386/all/glade3-3.4.5.tgz
> can't open /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me/pkg/DESCR
> at /usr/libdata/perl5/OpenBSD/Subst.pm line 85.
> ===> Cleaning for glade3-3.4.5
> rm -f /usr/ports/packages/i386/all/glade3-3.4.5.tgz
> /usr/ports/packages/i386/ftp/glade3-3.4.5.tgz
> /usr/ports/packages/i386/cdrom/glade3-3.4.5.tgz
> *** Error code 1
>
> Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
> 1424 of /usr/ports/infrastructure/mk/bsd.port.mk).
> *** Error code 1
>
> Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
> 1424 of /usr/ports/infrastructure/mk/bsd.port.mk).
> *** Error code 1
>
> Stop in /mnt/nept
Re: Glade3, anyone using/interested in a port?
good morning!
an update, some progress, and a request for help:
- I've attached my port-in-progress, along with some text files that
I've referenced/used in figuring this out (found under the "ref"
directory), and the Makefile is at the end of this email.
- all of the resources I've been pointed towards or found myself
(openbsd papers, the ports developer documentation, etc) have been
tremendously helpful, answering all of my questions thus far, the only
difficulty being dependency resolution.
- to resolve glade's dependencies, I have used several references,
and here is what I have so far:
- glade's own documentation mentions libxml2 and libglade as
runtime dependencies
- netbsd's glade3 port has a few "buildlinks" mainly: gtk2,
libxml2, hicolor-icon-theme, desktop-file-utils, libbonobui, and
libgnomeui
- the port-in-progress Jasper provided, also notes
textproc/scrollkeeper as a build/run-time dependency
- I don't really have a specific problem right now, but I know that
my Makefile isn't quite working correctly, which I believe stems from
having the correct dependencies (but I'm not sure).
Current state:
- I captured the contents of "libs.txt" during a run of make build.
This helps to show what the configure script found, stuck in glade's
Makefile, and is now set to be built during make build, but I also
expect that this helps determine the WANTLIB list.. is this a valid
assumption?
- I believe "make configure" works fine (output is included:
"make_configure.log")
- "make build" *seems* to work, but I'm skeptical because of the
issues that arise later, and because I still have the MODULES lines
commented out (the make build output is included as well:
"make_build.log"). I also don't really trust all of the DEPENDS lines
being complete.
- I have commented out the MODULES line because when it is present, I
get a lot of the following when running make build (as well as some
stuff about line 54):
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: Missing
dependency operator
"/usr/ports/infrastructure/mk/modules.port.mk", line 42: Could not
find /usr/ports/infrastructure/mk/\ .port.mk
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: warning:
Missing closing parenthesis for exists()
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: Malformed
conditional (exists(${PORTSDIR}/infrastructure/mk/\ .port.mk))
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: Missing
dependency operator
"/usr/ports/infrastructure/mk/modules.port.mk", line 42: Could not
find /usr/ports/infrastructure/mk/\ .port.mk
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: warning:
Missing closing parenthesis for exists()
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: Malformed
conditional (exists(${PORTSDIR}/infrastructure/mk/\ .port.mk))
"/usr/ports/infrastructure/mk/modules.port.mk", line 41: Missing
dependency operator
"/usr/ports/infrastructure/mk/modules.port.mk", line 42: Could not
find /usr/ports/infrastructure/mk/\ .port.mk
- I am currently a little confused by the output of the depends check
with "make port-lib-depends-check." The output can be seen in
ref/make_port-lib-depends-check.log. What I've determined is this:
- It appears WANTLIBS has entries glade3 doens't need, I'm
guessing this from the "Bogus WANTLIB" lines in the output. I simply
copy/pasted the WANTLIB line from the port-in-progress Jasper
provided, as I'm not sure how to determine these with accuracy.
- there are a few other libraries needed, as shown by: "WANTLIB
+= Xcomposite Xdamage iconv intl pcre pixman-1"
am I understanding this output correctly?
- make package doesn't work, showing that I've screwed up further back
along the line:
# make package
===> Looking for glade3-3.4.5.tgz in $PKG_PATH - not found
*** Error code 1
Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1416 of /usr/ports/infrastructure/mk/bsd.port.mk).
`/usr/obj/ports//glade3-3.4.5/fake-i386/.fake_done' is up to date.
===> Building package for glade3-3.4.5
Create /usr/ports/packages/i386/all/glade3-3.4.5.tgz
can't open /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me/pkg/DESCR
at /usr/libdata/perl5/OpenBSD/Subst.pm line 85.
===> Cleaning for glade3-3.4.5
rm -f /usr/ports/packages/i386/all/glade3-3.4.5.tgz
/usr/ports/packages/i386/ftp/glade3-3.4.5.tgz
/usr/ports/packages/i386/cdrom/glade3-3.4.5.tgz
*** Error code 1
Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1424 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1
Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1424 of /usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1
Stop in /mnt/neptune/Development/OpenBSD/ports/devel/glade3-me (line
1964 of /usr/ports/infrastructure/mk/bsd.port.mk).
# cat DESCR
Glade is a free user interface builder for GTK+ released under the GNU
General Public License (GPL). (GTK+, which stands for the Gimp ToolKit,
is a library for creat
Re: Glade3, anyone using/interested in a port?
On Thu, Nov 6, 2008 at 6:38 AM, Thomas Pfaff <[EMAIL PROTECTED]> wrote: > On Wed, 5 Nov 2008 21:44:07 -0500 > "Jason Beaudoin" <[EMAIL PROTECTED]> wrote: > >> Hey folks! >> >> I'm interested in using glade3 on openbsd [...] > > So am I. I started working on a port a while back, but I lacked the > time to complete it (or even get it working). If you decide to start > working on a port, I'm definitely willing to test it on my systems > and, if time permits, help make it work properly. > > Thomas > Thank you, everyone, for all the pointers, starter hints and support! I shall take the port in progress that Jasper provided, and keep things rolling. I am currently unemployed (but hopefully that will change after my interviews today and tomorrow!), so projects like this have been great, and I expect to have something ready for comments and clean up later today. Thanks again! ~Jason
Re: Glade3, anyone using/interested in a port?
On 2008/11/05 23:43, Jason Beaudoin wrote: > while the ports checklist has been helpful, there isn't much out there > about getting the build process to work when it fails on you. Should I > be looking in bsd.port.mk for more information? (I am currently having > trouble getting ports to run the configure script and generate a > Makefile for gmake.) There are a couple of ports tutorials with slides available at http://www.openbsd.org/events.html which could be useful. If you have a specific problem where you'd like some pointers, mail with the exact output you're getting, and please include the work-in-progress port (ideally with the whole thing as a tar and also paste the Makefile right in the message, it's easier to read and comment on it that way).
Re: Glade3, anyone using/interested in a port?
On Wed, Nov 5, 2008 at 8:43 PM, Jason Beaudoin <[EMAIL PROTECTED]> wrote: > while the ports checklist has been helpful, there isn't much out there > about getting the build process to work when it fails on you. Should I > be looking in bsd.port.mk for more information? (I am currently having > trouble getting ports to run the configure script and generate a > Makefile for gmake.) Reading the .mk files in infrastructure/mk directory as well as bsd.port.mk(5) are very helpful. What I can suggest is looking for another port with a similar make/build structure and see how it was done and try to mimic it. --patrick
Re: Glade3, anyone using/interested in a port?
> there are devel/libglade and devel/libglade2 > > Regards, > Markus > devel/libglade2 is a runtime dependency, I'm talking about devel/glade (the GTK+2 interface builder). I found that NetBSD has glade3 in pkgsrc, but I quickly gave up on trying to understand their framework. I'm in the process (and slowly making progress) at building my first port here. while the ports checklist has been helpful, there isn't much out there about getting the build process to work when it fails on you. Should I be looking in bsd.port.mk for more information? (I am currently having trouble getting ports to run the configure script and generate a Makefile for gmake.) thanks! ~Jason
Re: Glade3, anyone using/interested in a port?
On Wed, Nov 05, 2008 at 09:44:07PM -0500, Jason Beaudoin wrote: > Hey folks! Hello, > I'm interested in using glade3 on openbsd, but noticed that there was > no current glade port available. It appears that there once was, long, > long ago, but no longer. Several questions resulted: > > . what happened to the port for the older versions of glade, I don't > seem to have a devel/glade in my tree, though there have been recent > (last 2 months) changes noted in ports-cvs.. am I just being > incompetent in my port-finding skills? there are devel/libglade and devel/libglade2 Regards, Markus
Glade3, anyone using/interested in a port?
Hey folks! I'm interested in using glade3 on openbsd, but noticed that there was no current glade port available. It appears that there once was, long, long ago, but no longer. Several questions resulted: . does anyone have a (working or not) port of glade3 for OpenBSD that you've used, or were hacking on? . if not, is there any interest in having one added to the tree? (or rather, is there anything preventing this, licensing or otherwise?) . what happened to the port for the older versions of glade, I don't seem to have a devel/glade in my tree, though there have been recent (last 2 months) changes noted in ports-cvs.. am I just being incompetent in my port-finding skills? . If this older port exists, I'm assuming a new maintainer wouldn't hurt? either way, I'll take a stab at getting a port together, and maybe have something for you all to pick apart sometime soon. thanks, ~Jason
