Charles Wilson wrote:
> On 9/8/2010 11:59 AM, Earnie wrote:
>> Charles Wilson wrote:
>>> On 9/8/2010 9:31 AM, Chris Sutcliffe wrote:
>>>> I've packaged gdb 7.2 but I have 2 different binaries and I'm curious
>>>> how best to package it. Basically I have one gdb.exe that is python
>>>> enabled (linked against python27.dll) and one that is not. I'm
>>>> wondering if I should create 2 'bin' packages (one python, one not),
>>>> or one 'bin' package with gdb.exe and gdb-python.exe.
>>> My personal opinion is to package it in a single gdb pkg -- with lots of
>>> explanation in the RELEASE_NOTES file.
>> But that would cause the dependency on python always. IMO it should be
>> separate packages just for mingw-get purposes.
> Well, we don't actually PROVIDE any python package(s) -- and I doubt
> that we should. So, we can't actually *list* python in the mingw-get
> dependency list anyway. Even for a hypothetical gdb-python package, the
> only thing we CAN do is say, in the RELEASE_NOTES, "hey, if you want
> gdb-python to work you need to install python from
> http://www.python.org/, and then ensure that your PATH includes ..."
> At that point, why does it make any difference whether gdb-python is its
> own package, or if that binary is simply included in the same package as
> "regular" gdb? The only cost is a a few 10's of KB, after compression...
I'm convinced. One file.