summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20130401/d8c080c2/attachment-0001.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20130401/d8c080c2/attachment-0001.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20130401/d8c080c2/attachment-0001.html3
1 files changed, 3 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20130401/d8c080c2/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20130401/d8c080c2/attachment-0001.html
new file mode 100644
index 000000000..1dfc8af86
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130401/d8c080c2/attachment-0001.html
@@ -0,0 +1,3 @@
+<div dir="ltr"><div><div><div><div><div><div>I just noticed that both wcstools-devel and wcslib-devel create libraries named libwcs which causes a problem in linking to libwcs.so<br><br></div>Wondering if you have any thoughts on resolving the conflict.<br>
+<br></div>The other thing that I&#39;m wondering is if anyone has done a family tree of astronomy software.  It looks like there are three big families of professional astronomy tools<br><br></div>1) SAO - US tools <br></div>
+2) ESO <br></div>3) UK<br><br></div>Unfortunately we have a situation in which the WCS libraries from 1) and 2) end up colliding in name spaces.<br><br></div>