Thread: [Petitpoucet-user] gpsbabel patches to build library

Hi. I'm trying to create a portfile for petitpoucet for MacPorts; see:

http://trac.macports.org/ticket/15969

I'm discovering that petitpoucet requires a modified version of  
gpsbabel which installs a library. My question is why your patches to  
gpsbabel have not been included in gpsbabel itself. I would rather  
not have to patch gpsbabel in MacPorts. Besides, your patches  
provided with petitpoucet 0.1.4 are for gpsbabel 1.3.4 (or possibly  
1.3.2 [1]) but the version of gpsbabel in MacPorts is 1.3.5 so I'm  
not sure if the patches will still work.


[1] It's unclear; the user_guide.pdf says "There is no API and header  
stability with GPSBabel,  version 1.3.4 is required" but then says  
"Get GPSBabel source code version 1.3.2".


Unrelated: it would be great if you could excise the spam from the  
mailing list archives. Thanks.

Hello Ryan,

I will try to answer your questions...

Ryan Schmidt wrote:
> Hi. I'm trying to create a portfile for petitpoucet for MacPorts; see:
>
> http://trac.macports.org/ticket/15969
>   
That's cool.
What is the exact purpose ? A kind of Mac distribution of open-source 
software ?
> I'm discovering that petitpoucet requires a modified version of  
> gpsbabel which installs a library. My question is why your patches to  
> gpsbabel have not been included in gpsbabel itself. I would rather  
> not have to patch gpsbabel in MacPorts. Besides, your patches  
> provided with petitpoucet 0.1.4 are for gpsbabel 1.3.4 (or possibly  
> 1.3.2 [1]) but the version of gpsbabel in MacPorts is 1.3.5 so I'm  
> not sure if the patches will still work.
>
>   
We had a lot of trouble packaging GPSBabel for our application.
GPSBabel is an application, even worse a command line application. It is 
exiting at the first error and nothing is done to handle nicely errors 
nor continue executing on other tasks. For example, one of the input 
files is badly formed => application exits.

Our patches are trying to overcome these limitations with the minimum 
amount of modifications.
I have sent some of these to GPSBabel mailing list but did not get any 
acknowledgment.

Eventually, we got bored. Since release 0.1.4, we have changed our build 
system to CMake (as Open Scene Graph did) and now GPSBabel is part of 
our source code tree. It means I download GPSBabel source code, I patch 
it and I commit it to the SVN repository.

We are now working on the release 0.2. If you have any update/patch to 
submit, it is the right time. User guide has not been updated within 
SVN, it is on my todo list.
> [1] It's unclear; the user_guide.pdf says "There is no API and header  
> stability with GPSBabel,  version 1.3.4 is required" but then says  
> "Get GPSBabel source code version 1.3.2".
>   
That's a bug, both sentences will disappear at next update since 
GPSBabel is part of the source code.
>
> Unrelated: it would be great if you could excise the spam from the  
> mailing list archives. Thanks.
>
>   
I did some. It requires 3 clicks per message :-(

Thanks for all your feed-back.

Antoine

Hi Antoine Thanks for getting back to me.

On Jul 27, 2008, at 07:22, Antoine Hue wrote:

> Hello Ryan,
>
> I will try to answer your questions...
>
> Ryan Schmidt wrote:
>
>> Hi. I'm trying to create a portfile for petitpoucet for MacPorts;  
>> see:
>>
>> http://trac.macports.org/ticket/15969
>
> That's cool.
> What is the exact purpose ? A kind of Mac distribution of open-source
> software ?

MacPorts is a package manager for Mac OS X, like APT for Debian or  
Portage for Gentoo. It compiles and installs dependencies, informs  
you of available updates, and also makes uninstalling software easy.

>> I'm discovering that petitpoucet requires a modified version of
>> gpsbabel which installs a library. My question is why your patches to
>> gpsbabel have not been included in gpsbabel itself. I would rather
>> not have to patch gpsbabel in MacPorts. Besides, your patches
>> provided with petitpoucet 0.1.4 are for gpsbabel 1.3.4 (or possibly
>> 1.3.2 [1]) but the version of gpsbabel in MacPorts is 1.3.5 so I'm
>> not sure if the patches will still work.
>
> We had a lot of trouble packaging GPSBabel for our application.
> GPSBabel is an application, even worse a command line application.  
> It is
> exiting at the first error and nothing is done to handle nicely errors
> nor continue executing on other tasks. For example, one of the input
> files is badly formed => application exits.
>
> Our patches are trying to overcome these limitations with the minimum
> amount of modifications.
> I have sent some of these to GPSBabel mailing list but did not get any
> acknowledgment.
>
> Eventually, we got bored. Since release 0.1.4, we have changed our  
> build
> system to CMake (as Open Scene Graph did) and now GPSBabel is part of
> our source code tree. It means I download GPSBabel source code, I  
> patch
> it and I commit it to the SVN repository.

Ok, great. Then I don't need to worry about patching the gpsbabel port.

I understand petitpoucet also requires virtualplanetbuilder so I need  
to make a portfile for that first. Then I'll come back and see where  
I am with petitpoucet.

> We are now working on the release 0.2. If you have any update/patch to
> submit, it is the right time. User guide has not been updated within
> SVN, it is on my todo list.
>
>> [1] It's unclear; the user_guide.pdf says "There is no API and header
>> stability with GPSBabel,  version 1.3.4 is required" but then says
>> "Get GPSBabel source code version 1.3.2".
>
> That's a bug, both sentences will disappear at next update since
> GPSBabel is part of the source code.
>
>> Unrelated: it would be great if you could excise the spam from the
>> mailing list archives. Thanks.
>
> I did some. It requires 3 clicks per message :-(

:-(

> Thanks for all your feed-back.