My 2.28 build status

[Tiago "Salvador" Souza]

Hello,

I've commited the latest changes to the build system. packages are as
usual available on
http://www.4shared.com/dir/20334730/a267cd83/228.html.

Current status is, I am stuck with libunique, which is required by
brasero. The build won't fail but a bunch of errors are generated when
it doesn't find unique-1.0.pc, which is funny considering that's what we
are building. If anyone wants to pickup the work, I will be away from
the internet this weekend.

By the way, I have found a little issue on the nss and nspr packages and
I've added proper pkgconfig files for both, and fixed an issue with nss
that had some missing libs.

Best Wishes,
-  
Tiago "Salvador" Souza



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

2009/10/10 Tiago "Salvador" Souza <ts.salvador@...>:
> Hello,
>
> I've commited the latest changes to the build system. packages are as
> usual available on
> http://www.4shared.com/dir/20334730/a267cd83/228.html.

Good !!!

>
> Current status is, I am stuck with libunique, which is required by
> brasero. The build won't fail but a bunch of errors are generated when
> it doesn't find unique-1.0.pc, which is funny considering that's what we
> are building. If anyone wants to pickup the work, I will be away from
> the internet this weekend.

I dont get you wtf are you building brasero at that stage ? Was this
in some build order before
from somewhere ??? IMHO brasero should be built when we have the
Desktop up and running.
Dont loose time with this.

>
> By the way, I have found a little issue on the nss and nspr packages and
> I've added proper pkgconfig files for both, and fixed an issue with nss
> that had some missing libs.
>

Good work Tiago !

> Best Wishes,
> -
> Tiago "Salvador" Souza
>
>
Rgds
Saxa

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Tiago "Salvador" Souza]

> >
> > Current status is, I am stuck with libunique, which is required by
> > brasero. The build won't fail but a bunch of errors are generated when
> > it doesn't find unique-1.0.pc, which is funny considering that's what we
> > are building. If anyone wants to pickup the work, I will be away from
> > the internet this weekend.
>
> I dont get you wtf are you building brasero at that stage ? Was this
> in some build order before
> from somewhere ??? IMHO brasero should be built when we have the
> Desktop up and running.
> Dont loose time with this.
>

Just following the list of packages (which is more or less on alphabetic
order) from http://live.gnome.org/TwoPointTwentyseven/Desktop . Either
way, I've got it built and working apparently just fine. Again, I am
pretty sure brasero ain't "needed" for the basic desktop, but I don't
know which packages are (other than gnome-session, gconf, gvfs,
gnome-panel). Just going all the way from that list because I know if
something is required, it will prompt out and ask for it, this way we
can also know which package requires what for future reference.

Anyway, I believe libunique might be needed by some other packages. I've
made a very ugly hack to get it to compile properly. (copying over a
pkgconfig file to the root filesystem because setting the
PKG_CONFIG_PATH env variable from DBS doesn't seem to work). The issue
is, in order to build, it is requiring unique-1.0.pc, which is provided
by the same package, there are two ways to solve this, either adjust the
PKG_CONFIG_PATH env variable OR copy it to /usr/$LIB_DIR/pkgconfig and
build. The first one (the right way) doesn't work from DBS. No matter
how hard I try to export, or set the variable it doesn't work, so I've
done it the second way for now, while I wait for your opinion. This is
the first time I run into an issue like that, is it worth to go down to
try to get a fix into DBS just for that or should we go with the hack?

The "hack" is the following:

if [ ! -e $LIB_DIR/pkgconfig/unique-1.0.pc ]
then
        make "unique-1.0.pc"
        spewdo "cp $PKG_WORKROOT/$NAME-$VERSION/unique-1.0.pc
$LIB_DIR/pkgconfig/"
        COPIED_UNIQUE_PKGCONFIG="true"
fi


-  
Tiago "Salvador" Souza





------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

2009/10/12 Tiago "Salvador" Souza <ts.salvador@...>:

>
>
>> >
>> > Current status is, I am stuck with libunique, which is required by
>> > brasero. The build won't fail but a bunch of errors are generated when
>> > it doesn't find unique-1.0.pc, which is funny considering that's what we
>> > are building. If anyone wants to pickup the work, I will be away from
>> > the internet this weekend.
>>
>> I dont get you wtf are you building brasero at that stage ? Was this
>> in some build order before
>> from somewhere ??? IMHO brasero should be built when we have the
>> Desktop up and running.
>> Dont loose time with this.
>>
>
> Just following the list of packages (which is more or less on alphabetic
> order) from http://live.gnome.org/TwoPointTwentyseven/Desktop . Either

Wrong ! Dont follow alphabetic order lists, and the page on gnome.org
was never made in correct order.
Follow our previous build order.

> way, I've got it built and working apparently just fine. Again, I am
> pretty sure brasero ain't "needed" for the basic desktop, but I don't
> know which packages are (other than gnome-session, gconf, gvfs,
> gnome-panel). Just going all the way from that list because I know if
> something is required, it will prompt out and ask for it, this way we
> can also know which package requires what for future reference.
>

As I said before. Follow _our_ build order from before. Dont need to
reinvent the wheel.
Brasero probably need some other stuff than the one you have built and
so on. That other stuff
probably need other thing you have not yet built , this will result in
a non fully working packages.

> Anyway, I believe libunique might be needed by some other packages. I've
> made a very ugly hack to get it to compile properly. (copying over a
> pkgconfig file to the root filesystem because setting the
> PKG_CONFIG_PATH env variable from DBS doesn't seem to work). The issue
> is, in order to build, it is requiring unique-1.0.pc, which is provided
> by the same package, there are two ways to solve this, either adjust the
> PKG_CONFIG_PATH env variable OR copy it to /usr/$LIB_DIR/pkgconfig and
> build. The first one (the right way) doesn't work from DBS. No matter
> how hard I try to export, or set the variable it doesn't work, so I've
> done it the second way for now, while I wait for your opinion. This is
> the first time I run into an issue like that, is it worth to go down to
> try to get a fix into DBS just for that or should we go with the hack?
>

I will check this, but afaik we had libunique built before,  and it should work.

> The "hack" is the following:
>
> if [ ! -e $LIB_DIR/pkgconfig/unique-1.0.pc ]
> then
>        make "unique-1.0.pc"
>        spewdo "cp $PKG_WORKROOT/$NAME-$VERSION/unique-1.0.pc
> $LIB_DIR/pkgconfig/"
>        COPIED_UNIQUE_PKGCONFIG="true"
> fi
>
>

What is COPIED_UNIQUE_PKGCONFIG="true" for ????

Rgds
Saxa

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Tiago "Salvador" Souza]

Em Ter, 2009-10-13 às 07:37 +0200, Sasa Ostrouska escreveu:

> 2009/10/12 Tiago "Salvador" Souza <ts.salvador@...>:
> >
> >
> >> >
> >> > Current status is, I am stuck with libunique, which is required by
> >> > brasero. The build won't fail but a bunch of errors are generated when
> >> > it doesn't find unique-1.0.pc, which is funny considering that's what we
> >> > are building. If anyone wants to pickup the work, I will be away from
> >> > the internet this weekend.
> >>
> >> I dont get you wtf are you building brasero at that stage ? Was this
> >> in some build order before
> >> from somewhere ??? IMHO brasero should be built when we have the
> >> Desktop up and running.
> >> Dont loose time with this.
> >>
> >
> > Just following the list of packages (which is more or less on alphabetic
> > order) from http://live.gnome.org/TwoPointTwentyseven/Desktop . Either
>
> Wrong ! Dont follow alphabetic order lists, and the page on gnome.org
> was never made in correct order.
> Follow our previous build order.

I know it is not in the correct order, but I am building all the
required deps and testing the packages. My idea is that eventually I
should be able to implement a small dependency tracking tool into dbs to
assist us into building. I see that we had something like that planned
up to a point, hopefully this will be more useful :)

>
> > way, I've got it built and working apparently just fine. Again, I am
> > pretty sure brasero ain't "needed" for the basic desktop, but I don't
> > know which packages are (other than gnome-session, gconf, gvfs,
> > gnome-panel). Just going all the way from that list because I know if
> > something is required, it will prompt out and ask for it, this way we
> > can also know which package requires what for future reference.
> >
>
> As I said before. Follow _our_ build order from before. Dont need to
> reinvent the wheel.
> Brasero probably need some other stuff than the one you have built and
> so on. That other stuff
> probably need other thing you have not yet built , this will result in
> a non fully working packages.

> > Anyway, I believe libunique might be needed by some other packages. I've
> > made a very ugly hack to get it to compile properly. (copying over a
> > pkgconfig file to the root filesystem because setting the
> > PKG_CONFIG_PATH env variable from DBS doesn't seem to work). The issue
> > is, in order to build, it is requiring unique-1.0.pc, which is provided
> > by the same package, there are two ways to solve this, either adjust the
> > PKG_CONFIG_PATH env variable OR copy it to /usr/$LIB_DIR/pkgconfig and
> > build. The first one (the right way) doesn't work from DBS. No matter
> > how hard I try to export, or set the variable it doesn't work, so I've
> > done it the second way for now, while I wait for your opinion. This is
> > the first time I run into an issue like that, is it worth to go down to
> > try to get a fix into DBS just for that or should we go with the hack?
> >
>
> I will check this, but afaik we had libunique built before,  and it should work.
>
> > The "hack" is the following:
> >
> > if [ ! -e $LIB_DIR/pkgconfig/unique-1.0.pc ]
> > then
> >        make "unique-1.0.pc"
> >        spewdo "cp $PKG_WORKROOT/$NAME-$VERSION/unique-1.0.pc
> > $LIB_DIR/pkgconfig/"
> >        COPIED_UNIQUE_PKGCONFIG="true"
> > fi
> >
> >
>
> What is COPIED_UNIQUE_PKGCONFIG="true" for ????

Just a var to try to remove the unique-1.0.pc file in case it was added
to the actual system when building, to reduce the file system polution,
doesn't work on all cases though (like if you interrupt the script it
will remain there).

That behavior is caused by gobject-introspection, a new dependency by
policykit. If you compile the libunique BEFORE you compile
gobject-introspection it build files, if you do it afterwards, it fails
unless you explicitly disable introspection through configure (by
default it auto detects).

Suggestions?

>
> Rgds
> Saxa
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dropline-gnome-devel@...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

2009/10/14 Tiago "Salvador" Souza <ts.salvador@...>:

>
> Em Ter, 2009-10-13 às 07:37 +0200, Sasa Ostrouska escreveu:
>> 2009/10/12 Tiago "Salvador" Souza <ts.salvador@...>:
>> >
>> >
>> >> >
>> >> > Current status is, I am stuck with libunique, which is required by
>> >> > brasero. The build won't fail but a bunch of errors are generated when
>> >> > it doesn't find unique-1.0.pc, which is funny considering that's what we
>> >> > are building. If anyone wants to pickup the work, I will be away from
>> >> > the internet this weekend.
>> >>
>> >> I dont get you wtf are you building brasero at that stage ? Was this
>> >> in some build order before
>> >> from somewhere ??? IMHO brasero should be built when we have the
>> >> Desktop up and running.
>> >> Dont loose time with this.
>> >>
>> >
>> > Just following the list of packages (which is more or less on alphabetic
>> > order) from http://live.gnome.org/TwoPointTwentyseven/Desktop . Either
>>
>> Wrong ! Dont follow alphabetic order lists, and the page on gnome.org
>> was never made in correct order.
>> Follow our previous build order.
>
> I know it is not in the correct order, but I am building all the
> required deps and testing the packages. My idea is that eventually I
> should be able to implement a small dependency tracking tool into dbs to
> assist us into building. I see that we had something like that planned
> up to a point, hopefully this will be more useful :)

Why dont you use showdeps.py ????

>
>
>>
>> > way, I've got it built and working apparently just fine. Again, I am
>> > pretty sure brasero ain't "needed" for the basic desktop, but I don't
>> > know which packages are (other than gnome-session, gconf, gvfs,
>> > gnome-panel). Just going all the way from that list because I know if
>> > something is required, it will prompt out and ask for it, this way we
>> > can also know which package requires what for future reference.
>> >
>>
>> As I said before. Follow _our_ build order from before. Dont need to
>> reinvent the wheel.
>> Brasero probably need some other stuff than the one you have built and
>> so on. That other stuff
>> probably need other thing you have not yet built , this will result in
>> a non fully working packages.
>
>> > Anyway, I believe libunique might be needed by some other packages. I've
>> > made a very ugly hack to get it to compile properly. (copying over a
>> > pkgconfig file to the root filesystem because setting the
>> > PKG_CONFIG_PATH env variable from DBS doesn't seem to work). The issue
>> > is, in order to build, it is requiring unique-1.0.pc, which is provided
>> > by the same package, there are two ways to solve this, either adjust the
>> > PKG_CONFIG_PATH env variable OR copy it to /usr/$LIB_DIR/pkgconfig and
>> > build. The first one (the right way) doesn't work from DBS. No matter
>> > how hard I try to export, or set the variable it doesn't work, so I've
>> > done it the second way for now, while I wait for your opinion. This is
>> > the first time I run into an issue like that, is it worth to go down to
>> > try to get a fix into DBS just for that or should we go with the hack?
>> >
>>
>> I will check this, but afaik we had libunique built before,  and it should work.
>>
>> > The "hack" is the following:
>> >
>> > if [ ! -e $LIB_DIR/pkgconfig/unique-1.0.pc ]
>> > then
>> >        make "unique-1.0.pc"
>> >        spewdo "cp $PKG_WORKROOT/$NAME-$VERSION/unique-1.0.pc
>> > $LIB_DIR/pkgconfig/"
>> >        COPIED_UNIQUE_PKGCONFIG="true"
>> > fi
>> >
>> >
>>
>> What is COPIED_UNIQUE_PKGCONFIG="true" for ????
>
>
> Just a var to try to remove the unique-1.0.pc file in case it was added
> to the actual system when building, to reduce the file system polution,
> doesn't work on all cases though (like if you interrupt the script it
> will remain there).

Would not it be easier to do a single spwedo "rm $filename" ???

>
> That behavior is caused by gobject-introspection, a new dependency by
> policykit. If you compile the libunique BEFORE you compile
> gobject-introspection it build files, if you do it afterwards, it fails
> unless you explicitly disable introspection through configure (by
> default it auto detects).
>
> Suggestions?

This is probably because of the build order. I'm not sure tough.

Rgds
Saxa

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Tiago "Salvador" Souza]

-  
Tiago "Salvador" Souza


Em Qua, 2009-10-14 às 08:18 +0200, Sasa Ostrouska escreveu:

> 2009/10/14 Tiago "Salvador" Souza <ts.salvador@...>:
> >
> > Em Ter, 2009-10-13 às 07:37 +0200, Sasa Ostrouska escreveu:
> >> 2009/10/12 Tiago "Salvador" Souza <ts.salvador@...>:
> >> >
> >> >
> >> >> >
> >> >> > Current status is, I am stuck with libunique, which is required by
> >> >> > brasero. The build won't fail but a bunch of errors are generated when
> >> >> > it doesn't find unique-1.0.pc, which is funny considering that's what we
> >> >> > are building. If anyone wants to pickup the work, I will be away from
> >> >> > the internet this weekend.
> >> >>
> >> >> I dont get you wtf are you building brasero at that stage ? Was this
> >> >> in some build order before
> >> >> from somewhere ??? IMHO brasero should be built when we have the
> >> >> Desktop up and running.
> >> >> Dont loose time with this.
> >> >>
> >> >
> >> > Just following the list of packages (which is more or less on alphabetic
> >> > order) from http://live.gnome.org/TwoPointTwentyseven/Desktop . Either
> >>
> >> Wrong ! Dont follow alphabetic order lists, and the page on gnome.org
> >> was never made in correct order.
> >> Follow our previous build order.
> >
> > I know it is not in the correct order, but I am building all the
> > required deps and testing the packages. My idea is that eventually I
> > should be able to implement a small dependency tracking tool into dbs to
> > assist us into building. I see that we had something like that planned
> > up to a point, hopefully this will be more useful :)
>
> Why dont you use showdeps.py ????

Never saw that one before!

>
> >
> >
> >>
> >> > way, I've got it built and working apparently just fine. Again, I am
> >> > pretty sure brasero ain't "needed" for the basic desktop, but I don't
> >> > know which packages are (other than gnome-session, gconf, gvfs,
> >> > gnome-panel). Just going all the way from that list because I know if
> >> > something is required, it will prompt out and ask for it, this way we
> >> > can also know which package requires what for future reference.
> >> >
> >>
> >> As I said before. Follow _our_ build order from before. Dont need to
> >> reinvent the wheel.
> >> Brasero probably need some other stuff than the one you have built and
> >> so on. That other stuff
> >> probably need other thing you have not yet built , this will result in
> >> a non fully working packages.
> >
> >> > Anyway, I believe libunique might be needed by some other packages. I've
> >> > made a very ugly hack to get it to compile properly. (copying over a
> >> > pkgconfig file to the root filesystem because setting the
> >> > PKG_CONFIG_PATH env variable from DBS doesn't seem to work). The issue
> >> > is, in order to build, it is requiring unique-1.0.pc, which is provided
> >> > by the same package, there are two ways to solve this, either adjust the
> >> > PKG_CONFIG_PATH env variable OR copy it to /usr/$LIB_DIR/pkgconfig and
> >> > build. The first one (the right way) doesn't work from DBS. No matter
> >> > how hard I try to export, or set the variable it doesn't work, so I've
> >> > done it the second way for now, while I wait for your opinion. This is
> >> > the first time I run into an issue like that, is it worth to go down to
> >> > try to get a fix into DBS just for that or should we go with the hack?
> >> >
> >>
> >> I will check this, but afaik we had libunique built before,  and it should work.
> >>
> >> > The "hack" is the following:
> >> >
> >> > if [ ! -e $LIB_DIR/pkgconfig/unique-1.0.pc ]
> >> > then
> >> >        make "unique-1.0.pc"
> >> >        spewdo "cp $PKG_WORKROOT/$NAME-$VERSION/unique-1.0.pc
> >> > $LIB_DIR/pkgconfig/"
> >> >        COPIED_UNIQUE_PKGCONFIG="true"
> >> > fi
> >> >
> >> >
> >>
> >> What is COPIED_UNIQUE_PKGCONFIG="true" for ????
> >
> >
> > Just a var to try to remove the unique-1.0.pc file in case it was added
> > to the actual system when building, to reduce the file system polution,
> > doesn't work on all cases though (like if you interrupt the script it
> > will remain there).
>
> Would not it be easier to do a single spwedo "rm $filename" ???
>

No, because if by any chance the person building the package already has
a previous version of it installed it will be removed. That's why I
first check if the said file is there in the first place, if it is not,
it builds and puts into place, if it is not, it doesn't do anything and
simply builds the package

> >

> > That behavior is caused by gobject-introspection, a new dependency by
> > policykit. If you compile the libunique BEFORE you compile
> > gobject-introspection it build files, if you do it afterwards, it fails
> > unless you explicitly disable introspection through configure (by
> > default it auto detects).
> >
> > Suggestions?
>
> This is probably because of the build order. I'm not sure tough.

Yes and no. If you don't explicitly disable then it is affected by the
order. Either way order itself shouldn't affect my packages. I am
building all of them on a clean file system and installing only its deps
(and what else is required, along with the deps of the deps and so on).

Anyway. it builds fine now :)

>
> Rgds
> Saxa
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dropline-gnome-devel@...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

2009/10/15 Tiago "Salvador" Souza <ts.salvador@...>:

>
> -
> Tiago "Salvador" Souza
>
>
> Em Qua, 2009-10-14 às 08:18 +0200, Sasa Ostrouska escreveu:
>> 2009/10/14 Tiago "Salvador" Souza <ts.salvador@...>:
>> >
>> > Em Ter, 2009-10-13 às 07:37 +0200, Sasa Ostrouska escreveu:
>> >> 2009/10/12 Tiago "Salvador" Souza <ts.salvador@...>:
>> >> >
>> >> >
>> >> >> >
>> >> >> > Current status is, I am stuck with libunique, which is required by
>> >> >> > brasero. The build won't fail but a bunch of errors are generated when
>> >> >> > it doesn't find unique-1.0.pc, which is funny considering that's what we
>> >> >> > are building. If anyone wants to pickup the work, I will be away from
>> >> >> > the internet this weekend.
>> >> >>
>> >> >> I dont get you wtf are you building brasero at that stage ? Was this
>> >> >> in some build order before
>> >> >> from somewhere ??? IMHO brasero should be built when we have the
>> >> >> Desktop up and running.
>> >> >> Dont loose time with this.
>> >> >>
>> >> >
>> >> > Just following the list of packages (which is more or less on alphabetic
>> >> > order) from http://live.gnome.org/TwoPointTwentyseven/Desktop . Either
>> >>
>> >> Wrong ! Dont follow alphabetic order lists, and the page on gnome.org
>> >> was never made in correct order.
>> >> Follow our previous build order.
>> >
>> > I know it is not in the correct order, but I am building all the
>> > required deps and testing the packages. My idea is that eventually I
>> > should be able to implement a small dependency tracking tool into dbs to
>> > assist us into building. I see that we had something like that planned
>> > up to a point, hopefully this will be more useful :)
>>
>> Why dont you use showdeps.py ????
>
> Never saw that one before!
>
>>
>> >
>> >
>> >>
>> >> > way, I've got it built and working apparently just fine. Again, I am
>> >> > pretty sure brasero ain't "needed" for the basic desktop, but I don't
>> >> > know which packages are (other than gnome-session, gconf, gvfs,
>> >> > gnome-panel). Just going all the way from that list because I know if
>> >> > something is required, it will prompt out and ask for it, this way we
>> >> > can also know which package requires what for future reference.
>> >> >
>> >>
>> >> As I said before. Follow _our_ build order from before. Dont need to
>> >> reinvent the wheel.
>> >> Brasero probably need some other stuff than the one you have built and
>> >> so on. That other stuff
>> >> probably need other thing you have not yet built , this will result in
>> >> a non fully working packages.
>> >
>> >> > Anyway, I believe libunique might be needed by some other packages. I've
>> >> > made a very ugly hack to get it to compile properly. (copying over a
>> >> > pkgconfig file to the root filesystem because setting the
>> >> > PKG_CONFIG_PATH env variable from DBS doesn't seem to work). The issue
>> >> > is, in order to build, it is requiring unique-1.0.pc, which is provided
>> >> > by the same package, there are two ways to solve this, either adjust the
>> >> > PKG_CONFIG_PATH env variable OR copy it to /usr/$LIB_DIR/pkgconfig and
>> >> > build. The first one (the right way) doesn't work from DBS. No matter
>> >> > how hard I try to export, or set the variable it doesn't work, so I've
>> >> > done it the second way for now, while I wait for your opinion. This is
>> >> > the first time I run into an issue like that, is it worth to go down to
>> >> > try to get a fix into DBS just for that or should we go with the hack?
>> >> >
>> >>
>> >> I will check this, but afaik we had libunique built before,  and it should work.
>> >>
>> >> > The "hack" is the following:
>> >> >
>> >> > if [ ! -e $LIB_DIR/pkgconfig/unique-1.0.pc ]
>> >> > then
>> >> >        make "unique-1.0.pc"
>> >> >        spewdo "cp $PKG_WORKROOT/$NAME-$VERSION/unique-1.0.pc
>> >> > $LIB_DIR/pkgconfig/"
>> >> >        COPIED_UNIQUE_PKGCONFIG="true"
>> >> > fi
>> >> >
>> >> >
>> >>
>> >> What is COPIED_UNIQUE_PKGCONFIG="true" for ????
>> >
>> >
>> > Just a var to try to remove the unique-1.0.pc file in case it was added
>> > to the actual system when building, to reduce the file system polution,
>> > doesn't work on all cases though (like if you interrupt the script it
>> > will remain there).
>>
>> Would not it be easier to do a single spwedo "rm $filename" ???
>>
>
> No, because if by any chance the person building the package already has
> a previous version of it installed it will be removed. That's why I
> first check if the said file is there in the first place, if it is not,
> it builds and puts into place, if it is not, it doesn't do anything and
> simply builds the package
>

Ok but I dont get still what is the problem if you have an old
libunique installed ?
If it doesnt install the unique-1.0.pc it means something is wrong
with the sources and needs to be reported and complained with the
maintainer.
This simply because you cant just rebuild an package and if you
already have it installed it doesnt put the new .pc file in place.
This is completely
un understandable from my point of view. What if you change the prefix
of that lib then ? It will still leave the old .pc file on the system
???

>> >
>
>> > That behavior is caused by gobject-introspection, a new dependency by
>> > policykit. If you compile the libunique BEFORE you compile
>> > gobject-introspection it build files, if you do it afterwards, it fails
>> > unless you explicitly disable introspection through configure (by
>> > default it auto detects).
>> >
>> > Suggestions?
>>
>> This is probably because of the build order. I'm not sure tough.
>
> Yes and no. If you don't explicitly disable then it is affected by the
> order. Either way order itself shouldn't affect my packages. I am
> building all of them on a clean file system and installing only its deps
> (and what else is required, along with the deps of the deps and so on).
>
> Anyway. it builds fine now :)
>
>>
>> Rgds
>> Saxa
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dropline-gnome-devel@...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dropline-gnome-devel@...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Tiago "Salvador" Souza]

> Ok but I dont get still what is the problem if you have an old
> libunique installed ?
> If it doesnt install the unique-1.0.pc it means something is wrong
> with the sources and needs to be reported and complained with the
> maintainer.

It looks like something is not correct with the package or the build
process itself. When building it with introspection enabled it can't
seem to find some libraries. The unique-1.0.pc is provided by the
package itself and it looks like if that file is on the PKG_CONFIG_PATH
the build process is able to find the needed headers and works just
fine. I am not being able to properly set the PKG_CONFIG_PATH
environment variable from the build script, hence why I had to find a
way around it.

> This simply because you cant just rebuild an package and if you
> already have it installed it doesnt put the new .pc file in place.
> This is completely
> un understandable from my point of view. What if you change the prefix
> of that lib then ? It will still leave the old .pc file on the system
> ???

If, by any chance, you already have the package installed when you are
re-building it, build will work because you already have pkconfig file
in place. I am the one not understanding what you are not
understanding :)

The check is just to make things less messy. If you already have the
file in your system, it doesn't do anything, if you don't, it copies
over it over, builds the package and tries to remove it afterwards.





------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

2009/10/15 Tiago "Salvador" Souza <ts.salvador@...>:

>
>> Ok but I dont get still what is the problem if you have an old
>> libunique installed ?
>> If it doesnt install the unique-1.0.pc it means something is wrong
>> with the sources and needs to be reported and complained with the
>> maintainer.
>
> It looks like something is not correct with the package or the build
> process itself. When building it with introspection enabled it can't
> seem to find some libraries. The unique-1.0.pc is provided by the
> package itself and it looks like if that file is on the PKG_CONFIG_PATH
> the build process is able to find the needed headers and works just
> fine. I am not being able to properly set the PKG_CONFIG_PATH
> environment variable from the build script, hence why I had to find a
> way around it.
>
>> This simply because you cant just rebuild an package and if you
>> already have it installed it doesnt put the new .pc file in place.
>> This is completely
>> un understandable from my point of view. What if you change the prefix
>> of that lib then ? It will still leave the old .pc file on the system
>> ???
>
> If, by any chance, you already have the package installed when you are
> re-building it, build will work because you already have pkconfig file
> in place. I am the one not understanding what you are not
> understanding :)
>
> The check is just to make things less messy. If you already have the
> file in your system, it doesn't do anything, if you don't, it copies
> over it over, builds the package and tries to remove it afterwards.
>

To make a long story short, building it right now without anything and
just by hand on my
gnome 2.22 machine, I got the following:

sasa@quadserv:~/Desktop/pack-libunique$ cat liblist.txt
.:
total 0
-rw-r--r-- 1 sasa users  0 2009-10-15 17:18 liblist.txt
drwxr-xr-x 5 sasa users 42 2009-10-15 17:17 usr/

./usr:
total 0
drwxr-xr-x 3 sasa users  23 2009-10-15 17:17 include/
drwxr-xr-x 3 sasa users 146 2009-10-15 17:17 lib/
drwxr-xr-x 3 sasa users  20 2009-10-15 17:17 share/

./usr/include:
total 0
drwxr-xr-x 3 sasa users 19 2009-10-15 17:17 unique-1.0/

./usr/include/unique-1.0:
total 0
drwxr-xr-x 2 sasa users 105 2009-10-15 17:17 unique/

./usr/include/unique-1.0/unique:
total 28
-rw-r--r-- 1 sasa users 1039 2009-10-15 17:17 unique.h
-rw-r--r-- 1 sasa users 5753 2009-10-15 17:17 uniqueapp.h
-rw-r--r-- 1 sasa users 4573 2009-10-15 17:17 uniquebackend.h
-rw-r--r-- 1 sasa users 3519 2009-10-15 17:17 uniquemessage.h
-rw-r--r-- 1 sasa users 2939 2009-10-15 17:17 uniqueversion.h

./usr/lib:
total 564
-rw-r--r-- 1 sasa users 372112 2009-10-15 17:17 libunique-1.0.a
-rwxr-xr-x 1 sasa users   1608 2009-10-15 17:17 libunique-1.0.la*
lrwxrwxrwx 1 sasa users     24 2009-10-15 17:17 libunique-1.0.so ->
libunique-1.0.so.0.100.2*
lrwxrwxrwx 1 sasa users     24 2009-10-15 17:17 libunique-1.0.so.0 ->
libunique-1.0.so.0.100.2*
-rwxr-xr-x 1 sasa users 199719 2009-10-15 17:17 libunique-1.0.so.0.100.2*
drwxr-xr-x 2 sasa users     26 2009-10-15 17:17 pkgconfig/

./usr/lib/pkgconfig:
total 4
-rw-r--r-- 1 sasa users 276 2009-10-15 17:17 unique-1.0.pc

./usr/share:
total 0
drwxr-xr-x 3 sasa users 17 2009-10-15 17:17 gtk-doc/

./usr/share/gtk-doc:
total 0
drwxr-xr-x 3 sasa users 19 2009-10-15 17:17 html/

./usr/share/gtk-doc/html:
total 4
drwxr-xr-x 2 sasa users 4096 2009-10-15 17:17 unique/

./usr/share/gtk-doc/html/unique:
total 164
-rw-r--r-- 1 sasa users 30926 2009-10-15 17:17 UniqueApp.html
-rw-r--r-- 1 sasa users 18455 2009-10-15 17:17 UniqueBackend.html
-rw-r--r-- 1 sasa users   654 2009-10-15 17:17 home.png
-rw-r--r-- 1 sasa users  3359 2009-10-15 17:17 index.html
-rw-r--r-- 1 sasa users  7475 2009-10-15 17:17 index.sgml
-rw-r--r-- 1 sasa users  9640 2009-10-15 17:17 ix01.html
-rw-r--r-- 1 sasa users   459 2009-10-15 17:17 left.png
-rw-r--r-- 1 sasa users  2853 2009-10-15 17:17 license.html
-rw-r--r-- 1 sasa users   472 2009-10-15 17:17 right.png
-rw-r--r-- 1 sasa users  4882 2009-10-15 17:17 style.css
-rw-r--r-- 1 sasa users 29511 2009-10-15 17:17 unique-Message-Data.html
-rw-r--r-- 1 sasa users  8017 2009-10-15 17:17
unique-Versioning-Information.html
-rw-r--r-- 1 sasa users  2747 2009-10-15 17:17 unique-overview.html
-rw-r--r-- 1 sasa users  6284 2009-10-15 17:17 unique.devhelp
-rw-r--r-- 1 sasa users  8107 2009-10-15 17:17 unique.devhelp2
-rw-r--r-- 1 sasa users   406 2009-10-15 17:17 up.png
sasa@quadserv:~/Desktop/pack-libunique$

As you can see, here it is ok, the unique-1.0.pc file is in place. So
most probably on your system there is something _wrong_.

Rgds
Saxa

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Tiago "Salvador" Souza]

Saxa,

Please install the gobject-introspection package and try again.

You are clearly not understanding what I am trying to say.

Best Wishes,
-  
Tiago "Salvador" Souza


Em Qui, 2009-10-15 às 17:15 +0200, Sasa Ostrouska escreveu:

> 2009/10/15 Tiago "Salvador" Souza <ts.salvador@...>:
> >
> >> Ok but I dont get still what is the problem if you have an old
> >> libunique installed ?
> >> If it doesnt install the unique-1.0.pc it means something is wrong
> >> with the sources and needs to be reported and complained with the
> >> maintainer.
> >
> > It looks like something is not correct with the package or the build
> > process itself. When building it with introspection enabled it can't
> > seem to find some libraries. The unique-1.0.pc is provided by the
> > package itself and it looks like if that file is on the PKG_CONFIG_PATH
> > the build process is able to find the needed headers and works just
> > fine. I am not being able to properly set the PKG_CONFIG_PATH
> > environment variable from the build script, hence why I had to find a
> > way around it.
> >
> >> This simply because you cant just rebuild an package and if you
> >> already have it installed it doesnt put the new .pc file in place.
> >> This is completely
> >> un understandable from my point of view. What if you change the prefix
> >> of that lib then ? It will still leave the old .pc file on the system
> >> ???
> >
> > If, by any chance, you already have the package installed when you are
> > re-building it, build will work because you already have pkconfig file
> > in place. I am the one not understanding what you are not
> > understanding :)
> >
> > The check is just to make things less messy. If you already have the
> > file in your system, it doesn't do anything, if you don't, it copies
> > over it over, builds the package and tries to remove it afterwards.
> >
>
> To make a long story short, building it right now without anything and
> just by hand on my
> gnome 2.22 machine, I got the following:
>
> sasa@quadserv:~/Desktop/pack-libunique$ cat liblist.txt
> .:
> total 0
> -rw-r--r-- 1 sasa users  0 2009-10-15 17:18 liblist.txt
> drwxr-xr-x 5 sasa users 42 2009-10-15 17:17 usr/
>
> ./usr:
> total 0
> drwxr-xr-x 3 sasa users  23 2009-10-15 17:17 include/
> drwxr-xr-x 3 sasa users 146 2009-10-15 17:17 lib/
> drwxr-xr-x 3 sasa users  20 2009-10-15 17:17 share/
>
> ./usr/include:
> total 0
> drwxr-xr-x 3 sasa users 19 2009-10-15 17:17 unique-1.0/
>
> ./usr/include/unique-1.0:
> total 0
> drwxr-xr-x 2 sasa users 105 2009-10-15 17:17 unique/
>
> ./usr/include/unique-1.0/unique:
> total 28
> -rw-r--r-- 1 sasa users 1039 2009-10-15 17:17 unique.h
> -rw-r--r-- 1 sasa users 5753 2009-10-15 17:17 uniqueapp.h
> -rw-r--r-- 1 sasa users 4573 2009-10-15 17:17 uniquebackend.h
> -rw-r--r-- 1 sasa users 3519 2009-10-15 17:17 uniquemessage.h
> -rw-r--r-- 1 sasa users 2939 2009-10-15 17:17 uniqueversion.h
>
> ./usr/lib:
> total 564
> -rw-r--r-- 1 sasa users 372112 2009-10-15 17:17 libunique-1.0.a
> -rwxr-xr-x 1 sasa users   1608 2009-10-15 17:17 libunique-1.0.la*
> lrwxrwxrwx 1 sasa users     24 2009-10-15 17:17 libunique-1.0.so ->
> libunique-1.0.so.0.100.2*
> lrwxrwxrwx 1 sasa users     24 2009-10-15 17:17 libunique-1.0.so.0 ->
> libunique-1.0.so.0.100.2*
> -rwxr-xr-x 1 sasa users 199719 2009-10-15 17:17 libunique-1.0.so.0.100.2*
> drwxr-xr-x 2 sasa users     26 2009-10-15 17:17 pkgconfig/
>
> ./usr/lib/pkgconfig:
> total 4
> -rw-r--r-- 1 sasa users 276 2009-10-15 17:17 unique-1.0.pc
>
> ./usr/share:
> total 0
> drwxr-xr-x 3 sasa users 17 2009-10-15 17:17 gtk-doc/
>
> ./usr/share/gtk-doc:
> total 0
> drwxr-xr-x 3 sasa users 19 2009-10-15 17:17 html/
>
> ./usr/share/gtk-doc/html:
> total 4
> drwxr-xr-x 2 sasa users 4096 2009-10-15 17:17 unique/
>
> ./usr/share/gtk-doc/html/unique:
> total 164
> -rw-r--r-- 1 sasa users 30926 2009-10-15 17:17 UniqueApp.html
> -rw-r--r-- 1 sasa users 18455 2009-10-15 17:17 UniqueBackend.html
> -rw-r--r-- 1 sasa users   654 2009-10-15 17:17 home.png
> -rw-r--r-- 1 sasa users  3359 2009-10-15 17:17 index.html
> -rw-r--r-- 1 sasa users  7475 2009-10-15 17:17 index.sgml
> -rw-r--r-- 1 sasa users  9640 2009-10-15 17:17 ix01.html
> -rw-r--r-- 1 sasa users   459 2009-10-15 17:17 left.png
> -rw-r--r-- 1 sasa users  2853 2009-10-15 17:17 license.html
> -rw-r--r-- 1 sasa users   472 2009-10-15 17:17 right.png
> -rw-r--r-- 1 sasa users  4882 2009-10-15 17:17 style.css
> -rw-r--r-- 1 sasa users 29511 2009-10-15 17:17 unique-Message-Data.html
> -rw-r--r-- 1 sasa users  8017 2009-10-15 17:17
> unique-Versioning-Information.html
> -rw-r--r-- 1 sasa users  2747 2009-10-15 17:17 unique-overview.html
> -rw-r--r-- 1 sasa users  6284 2009-10-15 17:17 unique.devhelp
> -rw-r--r-- 1 sasa users  8107 2009-10-15 17:17 unique.devhelp2
> -rw-r--r-- 1 sasa users   406 2009-10-15 17:17 up.png
> sasa@quadserv:~/Desktop/pack-libunique$
>
> As you can see, here it is ok, the unique-1.0.pc file is in place. So
> most probably on your system there is something _wrong_.
>
> Rgds
> Saxa
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dropline-gnome-devel@...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

2009/10/15 Tiago "Salvador" Souza <ts.salvador@...>:
> Saxa,
>
> Please install the gobject-introspection package and try again.
>
> You are clearly not understanding what I am trying to say.
>

What is gobject-introspection package needed for ? And now I really
dont know anymore what you want to say.

Rgds
Saxa

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Tiago "Salvador" Souza]

Em Qui, 2009-10-15 às 20:59 +0200, Sasa Ostrouska escreveu:

> 2009/10/15 Tiago "Salvador" Souza <ts.salvador@...>:
> > Saxa,
> >
> > Please install the gobject-introspection package and try again.
> >
> > You are clearly not understanding what I am trying to say.
> >
>
> What is gobject-introspection package needed for ? And now I really
> dont know anymore what you want to say.

New dependency by policykit (which is now called polkit). I suspect some
other packages might be dependent or make use of it (like libunique can
make use of it, unless explicitly disabled).

>
> Rgds
> Saxa
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dropline-gnome-devel@...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel

[Sasa Ostrouska]

Thanks
Saxa

2009/10/16 Tiago "Salvador" Souza <ts.salvador@...>:

>
> Em Qui, 2009-10-15 às 20:59 +0200, Sasa Ostrouska escreveu:
>> 2009/10/15 Tiago "Salvador" Souza <ts.salvador@...>:
>> > Saxa,
>> >
>> > Please install the gobject-introspection package and try again.
>> >
>> > You are clearly not understanding what I am trying to say.
>> >
>>
>> What is gobject-introspection package needed for ? And now I really
>> dont know anymore what you want to say.
>
> New dependency by policykit (which is now called polkit). I suspect some
> other packages might be dependent or make use of it (like libunique can
> make use of it, unless explicitly disabled).
>
>>
>> Rgds
>> Saxa
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Dropline-gnome-devel mailing list
>> Dropline-gnome-devel@...
>> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dropline-gnome-devel@...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dropline-gnome-devel mailing list
Dropline-gnome-devel@...
https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel