How to know when to rebuild own packages
by aikempshall from LinuxQuestions.org on (#5135R)
Last week Pat updated glibmm.
Whilst rebuilding Inkscape, because of the recent upgrade to python3, I discovered that inkscape is dependent on glibmm. If the rebuild hadn't failed I would have never have known.
How do people, who build from SlackBuilds, know that they should rebuild certain packages when Pat upgrades a package in current/stable. I don't think any slackbuilds from SBO include in their requirements the packages that Pat supports.
Slackbuilds inkscape.info file has no mention of glibmm in it's requirements
Quote:
Whilst rebuilding Inkscape, because of the recent upgrade to python3, I discovered that inkscape is dependent on glibmm. If the rebuild hadn't failed I would have never have known.
How do people, who build from SlackBuilds, know that they should rebuild certain packages when Pat upgrades a package in current/stable. I don't think any slackbuilds from SBO include in their requirements the packages that Pat supports.
Slackbuilds inkscape.info file has no mention of glibmm in it's requirements
Quote:
| PRGNAM="inkscape" VERSION="20191115_a4ee55b" HOMEPAGE="http://www.inkscape.org/" DOWNLOAD="http://ponce.cc/slackware/sources/repo/inkscape-20191115_a4ee55b.tar.xz" MD5SUM="0421027cbfdd89497b38ba1ce87a01b9" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="GraphicsMagick gdl double-conversion lxml numpy potrace" MAINTAINER="Fernando Lopez Jr." EMAIL="fernando.lopezjr@gmail.com" |