Search found 8 matches
- Wed Oct 25, 2017 2:29 pm
- Forum: Open discussion
- Topic: Start Page is blank on 0.16.6712 (Manjaro)
- Replies: 8
- Views: 2382
Re: Start Page is blank on 0.16.6712 (Manjaro)
The webui was disabled when we removed qtwebkit, correct. Here's the commit that introduced this: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/freecad&id=6d86a3dc4d711fe2b180a0b0c8194f92a9ef6942 I'm not sure if I would have done it this way, but I didn't feel it neces...
- Thu Mar 30, 2017 6:32 pm
- Forum: Install / Compile
- Topic: Linux package maintainers: How to improve maintenance of FreeCAD packages?
- Replies: 18
- Views: 4343
Re: Linux package maintainers: How to improve maintenance of FreeCAD packages?
try this: cmake \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX:PATH="/usr/lib/freecad" \ -DCMAKE_INSTALL_DOCDIR:PATH="/usr/share/freecad/doc" \ -DCMAKE_INSTALL_DATADIR:PATH="/usr/share/freecad" \ -DOCC_INCLUDE_DIR:PATH=/opt/opencascade/inc/ \ -DPYTHON_EXECUTABLE...
- Thu Mar 30, 2017 9:23 am
- Forum: Install / Compile
- Topic: Linux package maintainers: How to improve maintenance of FreeCAD packages?
- Replies: 18
- Views: 4343
Re: Linux package maintainers: How to improve maintenance of FreeCAD packages?
I don't know what exactly the problem is. I assume inside /usr/bin you have the executable freecad or FreeCAD. What is it, the executable itself or a symlink? For the former case it would explain the behaviour because relative to the path of the executable it computes the path where it expects the ...
- Wed Mar 29, 2017 10:36 pm
- Forum: Install / Compile
- Topic: Linux package maintainers: How to improve maintenance of FreeCAD packages?
- Replies: 18
- Views: 4343
Re: Linux package maintainers: How to improve maintenance of FreeCAD packages?
I've recently got a report about an icon error (https://bugs.archlinux.org/task/53320) which brought me to this thread. FWIW I think installing freecad to match the Arch Linux' directory layout works rather well. One gripe I have is that I currently have to work around the mod dir being installed an...
- Tue Jan 24, 2017 12:26 pm
- Forum: Packaging
- Topic: Thread tracking different OS/Distro maintainers (creating more uniformity)
- Replies: 27
- Views: 8739
Re: Thread tracking different OS/Distro maintainers (creating more uniformity)
If you prefer that I build the Arch Linux package from the git repository, I can also do that, but I will still build from the tag (0.16 in this case), not from a branch. So at least in terms of what source I build, there would be no difference. The tag would not change when you push new release ta...
- Tue Jan 17, 2017 1:47 pm
- Forum: Packaging
- Topic: Thread tracking different OS/Distro maintainers (creating more uniformity)
- Replies: 27
- Views: 8739
Re: Thread tracking different OS/Distro maintainers (creating more uniformity)
When we provide a new release then we make a new branch and set these variables. So, this should work sufficiently well. The only missing information are the url and the date. However, when creating a package from the master branch this won't work well because the above information is always outdat...
- Tue Jan 17, 2017 1:30 pm
- Forum: Packaging
- Topic: Thread tracking different OS/Distro maintainers (creating more uniformity)
- Replies: 27
- Views: 8739
Re: Thread tracking different OS/Distro maintainers (creating more uniformity)
Edit: This reminds me that after I installed freecad-git on Arch, the icon was wrong (i.e. not using my icon theme) and I had to go to /usr/share/applications/freecad.desktop and change icon=/opt/freecad/data/freecad.xpm to icon=freecad. I guess this might be another packaging bug but I can't remem...
- Tue Jan 17, 2017 9:26 am
- Forum: Packaging
- Topic: Thread tracking different OS/Distro maintainers (creating more uniformity)
- Replies: 27
- Views: 8739
Re: Thread tracking different OS/Distro maintainers (creating more uniformity)
Let's say I'm a committer and I want to push the newest version of 0.16. I can run the following commands: g tag -f 0.16 # force updating g push origin :refs/tags/0.16 # delete on remote g push origin 0.16 # push tag pointed at new commit Please NEVER EVER change published tags. Other users that ha...