LibreCAD packaging for Fedora and RHEL-type systems
(RHEL = Red Hat Enterprise Linux™ which as a family includes
Scientific Linux, CentOS and others.
These sytems are derived from the same overall upstream project, Fedora.)
Downloads LibreCAD v1.0.0rc3:
LibreCAD v1.0.0rc2
Repo |
If you're bored and know a thing or two about rpm packaging on Fedora or EPEL please give the spec file a review and tell me what to fix about it, or how to make it more simple. If you're really bored, give the build scripts for qmake and make a look and give me some feedback. Building for Windows, Mac OS X and Linux may have things more complicated than they need be -- any simplifications (even Linux specific) are welcome. 2011.09.29
2011.09.26
2011.09.25
|
Why this page?
LibreCAD is the most exciting thing happening in open source CAD development today. Unfortunately it is not quite up to the project leader's standard for release just yet, but it is already a wonderfully useful program. Along with it not quite being ready for major release some of the compilation details make packaging an rpm up to the standards required by the Fedora community a bit of a pain. The rapid pace of current development also makes packaging for a serious distro like Fedora a bit of a pain (read as "more confusion than I currently have time for"). Instead of pushing for inclusion in Fedora and EPEL just yet, I decided to roll some independent packages for EPEL 6 and various versions of Fedora in the meantime.
But there are already LibreCAD packages for Debian and Ubuntu... and even some rpms for SuSE and [system X]!
I know. There are. The standards for things like FHS compliance and spec file writing are a bit
more strict/clash with other distro styles and I sincerely do not feel that LibreCAD is quite ready
for Fedora or EPEL just yet. If you feel differently, feel free to go become a Fedora package maintainer
and push through the review process now.
Why is this part of the site so ugly?
Because I made it by hand in a text editor, writing very little html markup in the process. I did this for a few reasons:
Why is your version number 1.0.0rcX but your package version number 0.0.X?
And finally, a good question.
I did not label the LibreCAD package version 1.0.0rc[whatever] because this gets in the way of package version control. Having letters at the end of your version numbers can confuse a package management system because "rc" isn't really part of a release number series, is it? For example, the package management software doesn't accept the word "version" in the file name and key off of it, instead most of them accept [package-name].[arch].[version] or some similar pattern and react that way. If they don't key off the word "version" then what would make one think they key off random letters like "rc"? A package name of "librecad-1.0.0rc2-el6.i686.rpm" doesn't tell the package manager the right thing, as "1.0.0rc2" could look like it is actually newer (that is, further along in precedence) than "1.0.0", which is wrong. To get around this requires some fanagling with the order and placement of the package name elements -- and Fedora has a system for this -- but if I follow that system here, and someone else goes to the trouble of really packaging LibreCAD for Fedora or EPEL before the actual v1.0 release then my repo will conflict or compete with their proper version numbers. Much easier for me to just arbitrarily invent a "0.0.X" release series here and be certain that anybody's distro package will take precedence over mine.
This whole repo is really only supposed to be active for a short time anyway...
[LibreCAD Wiki | LibreCAD Project Page | Project Home at GitHub | Project Home at SourceForge | LibreCAD IRC (#librecad at freenode)]