Hi,
I'm so super grateful that we now have a working Travis setup :)
As I suspected, there would be "problems" that we wouldn't be able to
discover on a test setup and this is one of them.
It's not really important to fix, but I wanted to mention it.
Link:
Hi
Taking a step back for a moment, why is an SQL database the best way
>> to store this data? What sorts of queries are you going to want to
>> run on it? Would a text (Tcl array) representation similar to the
>> PortIndex be a better fit?
>>
>>
>> We need to store all the
On 2017-6-22 02:09 , Umesh Singla wrote:
Hi Josh,
Taking a step back for a moment, why is an SQL database the best way
to store this data? What sorts of queries are you going to want to
run on it? Would a text (Tcl array) representation similar to the
PortIndex be a better fit?
>>
>> - it was slightly easier to switch the system compiler/stdlib (in
>> particur switching to the latest gcc on 10.5 for example)
That particular piece is fairly easy. Just put this in macports.conf:
default_compilers macports-gcc-6
and you're done. Every port will compile with gcc6,
Hi Josh,
Taking a step back for a moment, why is an SQL database the best way to
> store this data? What sorts of queries are you going to want to run on it?
> Would a text (Tcl array) representation similar to the PortIndex be a
> better fit?
>
We need to store all the information about the
Understood and agreed, Mojca. Again: It seems like keeping track of the
std c++ lib could be done by port & would have utility (mostly for
developers, but still). It would certainly beat adding compiler variants
to all C++ ports to get the c++ lib correct for dependents (as I did for
my test for
