SBo-git - slackbuilds.org on git (with patches for current)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
k9copy 6c59c38 multimedia/k9copy: added a patch for the new gcc in -current.
2.3.6 contains this patch, so you could just bump the version. Furthermore, in order to be able to copy without menus, when using the dvdauthor-0.7.0 slackbuild, one must configure dvdauthor with --enable-default-video-format=ntsc, as this is what k9copy expects.
I am having one problem. I've installed several things and when I open sbopkg and click packages, I get this message:
It appears you have no SBo-git packages installed.
You've found a bug in sbopkg. What happens is that we replace TAG internally with REPO_TAG and that's not getting passed to the SlackBuild so you'll probably find /var/log/packages is full of *_SBo packages when it should be full of *_custom packages. As a temporary workaround, if you run sbopkg like
Code:
TAG=_custom sbopkg ...
then sbopkg will pick *that* up and pass it on and everything will be as it should be: your packages will be built as $package_custom and sbopkg will list them properly.
And, of course, we'll try to get that bug fixed soon.
(If you have *_custom items in /var/log/packages and sbopkg isn't showing *those*, let me know, because that'd mean I misdiagnosed the bug.)
For the first time I've been able to compile chromium and getting it working.
I haven't touched chromium's slackbuild
P.S. for me the "packages" list works with a custom "ponce" TAG: is specified correctly in the repo file in /etc/sbopkg/repos.d and I have it exported in /etc/sbopkg/sbopkg.conf (but it works also if I omit it here).
You've found a bug in sbopkg. What happens is that we replace TAG internally with REPO_TAG and that's not getting passed to the SlackBuild so you'll probably find /var/log/packages is full of *_SBo packages when it should be full of *_custom packages. As a temporary workaround, if you run sbopkg like
Code:
TAG=_custom sbopkg ...
then sbopkg will pick *that* up and pass it on and everything will be as it should be: your packages will be built as $package_custom and sbopkg will list them properly.
And, of course, we'll try to get that bug fixed soon.
(If you have *_custom items in /var/log/packages and sbopkg isn't showing *those*, let me know, because that'd mean I misdiagnosed the bug.)
Hi slakmagik,
Thanks, TAG=custom sbopkg worked for me. Yes my packages were all sbopkg instead of custom. Do I need open sbopkg with TAG=custom sbopkg each time?
Hi slakmagik,
Thanks, TAG=custom sbopkg worked for me. Yes my packages were all sbopkg instead of custom. Do I need open sbopkg with TAG=custom sbopkg each time?
Glad it works for you. As far as each time, you should only need to when you're building packages, but that's likely most of the time. Or you could try adding the line
Code:
export TAG=$REPO_TAG
after line 3311 of 0.34.0. I haven't tested it but it may be all that's needed.
I added your repo as an unsupported repo. This way people will just have to select it from the menu or with the -V flag and not have to create the file if they want to use it. Is there anything you'd want to change? It occurs to me that '_custom' is an oddly vague tag and maybe '_SBoC' or 'ponce' or something might be good but that's entirely up to you.
thanks a lot for that slakmagik! \o/
I appreciate it and I have one more reason to keep it stable
I think "ponce" should do (to help avoid people go reporting bugs to busy slackbuilds.org's fellas while it's all my fault)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.