Re: Octave build dependencies wiki

[CdeMills]

Hello,

I think the main table as it is constructed today will become unreadable
over time. For now, we have
Task     Name    Usage   License / Copyright     Version        Debian  
ArchLinux        Level  
Recent CVE ?

The left column contains a task: build / documentation /external. I should
introduce one more category: plotting, including on-screen graphs and
printed graphs.

Name and Usage contains the package name as known from "configure" and
"pkgconfig".  Now, the translation between the package name and the packet
name, if we consider that each platform/distribution uses some kind of
package manager, is specific, with variations like libfontconfig-dev versus
libfontconfig-devel. If we start listing all those variations, I fear that
we'll end up with a gigantic table. Shouldn't we make one specific page per
distribution, with one association table "package name" - "packet name" ,
followed by the distribution-specific tips and tricks ?

Regards

Pascal




--
View this message in context: 
http://octave.1599824.n4.nabble.com/CVE-check-for-Octave-dependencies-tp4660188p4660307.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.