Re: [gnome-love] development

[Sean Kelley <sean sweng gmail com>]

Okay.  I created a bugzilla account and filed a bug report.  I really like Gnome's bugzilla layout.  It is very well done.

Sean

On 1/15/06, Sean Kelley <sean sweng gmail com> wrote:

Sorry to keep asking questions.  But there appears to be a problem with ftp://ftp.gnupg.org and trying to download libgpg-error-1.1 and libgcrypt-1.2.1.  It always times out.  I had to control-C jhbuild and go to mirrors, download those two files by hand, copy them to ~/cvs/gnome2/ and then restart jhbuild.  Should I file a bug report on this?

Thanks for the helpful pointers!

Sean

On 1/15/06, Luis Menina <liberforce fr st> wrote:

Hi Sean,
Had this problem a while ago... You can usally find some good tips about
compilation errors when using jhbuild on the Jhbuild Issues page:
http://live.gnome.org/JhbuildIssues

I had previously addes the solution to this problem, but forgot to add a
link to the pango page I created for that purpose ;-) . Now you will
find on the JhbuildIssues a link to problems about compiling pango... It
will lead you here: http://live.gnome.org/JhbuildIssues_2fpango

Please, don't hesitate to fill some bug reports for new problems, or put
them in the wiki jhbuild issue page...

This bug was entered in the gnome bugzilla:
http://bugzilla.gnome.org/show_bug.cgi?id=319632

I then reported it on freedesktop's bugzilla (this bug depends on how
you compiled cairo).
http://bugs.freedesktop.org/show_bug.cgi?id=5062

The issue is still open, but the link I gave you will show you a
workaround for this problem.

Have a nive time with Jhbuild (yes, still hard to have it working ;-) )

Luis Menina

Sean Kelley a écrit :
> Thanks.  I have started with jhbuild and am working through the links
> that you have provided.  I have encountered an error with
> Pango/examples.  In particular:
>
> ERROR.....undefined reference to `cairo_surface_write_to_png'
>
> I removed examples from the SUBDIR var of the Makefile in the pango
> directory and was able to resume the build.
>
> Sean
>
>
> On 1/13/06, *Elijah Newren * <newren gmail com
> <mailto: newren gmail com>> wrote:
>
>     On 1/13/06, Paolo Borelli < pborelli katamail com
>     <mailto: pborelli katamail com>> wrote:
>      > Hi Sean,
>      >
>      >         first of all let me give you some useful link ti get started:
>      >
>      > http://live.gnome.org/JoinGnome
>      > http://live.gnome.org/GnomeLove
>      > http://www.gnome.org/~newren/tutorials/developing-with-gnome
>     <http://www.gnome.org/~newren/tutorials/developing-with-gnome >
>
>     Another link, which I think is underused:
>       http://bugzilla.gnome.org/reports/gnome-love.cgi
>     that will take you to bugs marked by developers as being good projects
>     for people getting started.
>
>     In particular, I'd like to point out
>     http://bugzilla.gnome.org/show_bug.cgi?id=317405 ; I'm looking for a
>     volunteer to fix that one--I pointed out the function that needs to be
>     modified so that you don't need to search a big module for the right
>     place to get started.  :)
>
>     <snip>
>      > As you note, the best thing is getting started with contributing
>     to an
>      > app that you like and that you use: you can get in touch with
>     developers
>      > of such an app by finding them on irc and by subscribing to the
>     relevant
>      > mailing list. Another thing you can do is to check the current bugs
>      > filed in bugzilla.gnome.org <http://bugzilla.gnome.org > for such
>     an application and see if there is
>      > something you want to fix.
>
>     If you know you are interested in a certain project, the project's
>     overview page ( e.g.
>     http://bugzilla.gnome.org/browse.cgi?product=gossip) should prove
>     helpful.  It also contains a link (in the column at the right) to the
>     bugs for that product from the list I pointed out in the gnome-love
>     link above; of course, you can also try your hand at fixing any of the
>     other bugs as well and that page can help you look for them by
>     category more easily.
>
>     <snip>
>
>      > About building from cvs, it may seem a little dounting at the
>     beginning
>      > but it's not so hard: there is a build script named jhbuild which
>     may be
>      > very helpful (the links I gave you have more info about it).
>
>     My personal opinion is that this should be modified to read "it's not
>     so hard -- after you've already done it a couple times".  It's useful
>     to have others around to help you through the first time or two,
>     especially those that have built it recently and are familiar with the
>     recent issues.  Thus, staying on IRC and asking questions, in addition
>     to reading through a guide on building from CVS, can be quite helpful.
>
>     However, it does take quite a bit of time, especially compared to the
>     amount of time new people typically want to put in.
>
>      > Beside you don't need to build everything from cvs, you may just
>     build
>      > the base libraries (glib, gtk, etc) and the app you plan to work on
>      > (usually installing in a separate prefix) and continue to run your
>      > distro's desktop. Depending on how uptodate your distro is and
>     which app
>      > you want to work on, you may even skip building the libraries and
>     use
>      > the distro's devel packages
>
>     Metacity is a good example of this; your distro need not be too up to
>     date (Gnome 2.10 with the associated devel libraries is good enough)
>     and you should still be able to build it from cvs without having to
>     build any other modules from cvs.  There are probably a number of
>     other examples too; most at the application level but you could also
>     get the same effect by going low enough in the library stack.  :)
>
>
>     Cheers,
>     Elijah
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> gnome-love mailing list
> gnome-love gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-love