Hi all,

I recently decided to try again to build gnucash using sbopkg and slackbuilds.org. In the past, I've gotten tangled up in the dependencies and given up in frustration. The problem isn't with slackbuilds.org -- the dependencies are very well-documented! The problem isn't with sbopkg and it's queue functions, which are intelligent, logical, and powerful.

The problem is that some of gnucash's dependencies have dependencies that share dependencies with other dependencies. I was having trouble taking a branching chain of dependencies and translating it to a queue where each package is only listed once.

Last night I realized that I could create a flow chart showing the dependencies as branches and use that to identify the duplicated packages. After than, I created a queue file with each package listed only once and in the preferred order. It built without errors and gnucash is now running on my system.

I've attached the flow chart I created. The duplicate dependencies are in yellow. The resulting gnucash.sqf queue file is below.

gnucash.sqf
It's possible that I just "discovered" a tip that most people already know about and use. Nevertheless, I find creating a flow chart of the dependencies very helpful and thought I'd share it.

Regards,

Attached Thumbnails

 

That's the perfect opportunity for a bit of self-promotion. *cough* *cough*

I see you're on Slackware-14.0, well, comparing what's below with your nice chart, thankfully you won't have to do all that again; most of those deps are already in 14.1.

1 members found this post helpful.

So 55020 how much did you have to pay Lufbery to post his tree structure on the day* you announced the release of your software?

Will we be seeing related posts by others throughout the week? Or was this just a one day marketing campaign?

Congrats on your software.

* EDIT: Actually day after

Nice, and I like the flowchart.

This notwithstanding, what about this?

1 members found this post helpful.

It's open source. I didn't get paid a dime.

I'll check out slackrepo. It looks like it serves a real need.

Nevertheless, I think creating a flow chart of dependencies is a great way to check the sanity of your build order. QGIS is another one where, once you get into the optional dependencies, everything can become tangled with dependencies being dependencies of other dependencies.

I've been using Slackware since version 11 was released (late 2006), and I've been building 3rd party packages from source for nearly as long -- primarily using slackbuilds and src2pkg. I've also built Linux From Scratch -- with package management -- several times. I feel pretty good about my ability to build stuff from source, although I run into enough snags to not get cocky.

Anyway, it hit me last night that a flowchart is the perfect tool for documenting dependencies before coming up with the build order. It seems so obvious now that I can't believe I didn't think of it sometime in the prior six or seven years that I've been a slacker.

The marketing campaign will end in disaster when Lufbery asks if it will work in 14.0 and I will be forced to admit that it doesn't

If you like dependency graphs, then check this thread out.

2 members found this post helpful.

Wow! That's simply awesome.

Like I said, I probably just "discovered" something that everyone else already knows.