Hello!

I was very happy to see that dzen2 is now available on SlackBuilds.org because now I can use XMonad to its fullest. Unfortunately, sbopkg is not able to download the source code for dzen2. This is probably because the source is hosted on Google Code, which requires the user to click a second download link for some reason. I downloaded the source and the SlackBuild manually and installed dzen2 that way, and that worked perfectly, but I would really prefer to have sbopkg manage updates for me. Is there any way I could get this working? Perhaps I could just download the source manually, place it in the appropriate directory, and let sbopkg build it and manage updates, but I don't know which directory the source would go in or if this would even work.

Here is the link to the SlackBuilds.org page for dzen2: http://slackbuilds.org/repository/13.0/desktop/dzen2

Can anyone help me find a solution to this?

Thanks,
Agi93

If you manually build the SBo using the slackbuild steps, the package will still appear (and be included when sbopkg searches for updates) in the sbopkg list.
Even if you manually build with a newer version than sbopkg is aware of, it will figure this out.

The directory is /var/cache/sbopkg/

Wow, you're right! I didn't know sbopkg would be this smart!

Thanks for the information. I guess I'll just keep building manually when sbopkg tells me there's an update, or hopefully the maintainer can fix the download link somehow.

Yes, unfortunately some sources have annoying download links or redirects that make it difficult for wget (which is what sbopkg uses to fetch the source). There is some error checking that sbopkg does to try and fix these kinds of stupid links, but it is not perfect. I see that even the download link to dzen2 0.8.5 on the dzen homepage is actually to a file called "dzen2-latest.tar.gz" which is an extremely unhelpful naming convention. If you can find a better download link, please let the dzen2 maintainer know.

I am the previous maintainer of the dzen2 SBo script until Slackware 13.0 was released and i remember contacting the developer about this issue personally in the IRC and was supposed to have fixed this. But it seems theres still problems.