Hi ppl

Thks for yr replies,

@Slackd,@Shylock : Ok, I have already used sbopkg, but hand edited the SlackBuild in the interactive window to change ARCH, glad to hear it is automatic... :-)

@veeall : I will try this one... :-)

BRGDS

Alex

Sorry for the delay in responding ... you can file it in the "Issue Tracker" at the sbopkg Google Code page you linked to. The Issue Tracker is used for bug reports, feature requests etc.

tnx chess, just filed the feature request

Poncez, great thanks. That helps us keep track of things.

One thing I mentioned there that I will mention here in case someone else finds this thread is that sbopkg might already be able to do what you want. Look into creating a 'local' repo (i.e. a custom repo) where you can have your own packages. See the README-repos.d documentation file for more information.

I agree with this sentiment and am surprised that sbopkg is not prominently mentioned on the Slackbuilds website as a tool that can really enhance the usefulness of the site and its builds. As far as I could tell there was not even an sbopkg Slackbuild to be had from the site. How come ?

Bogus

I didn't want to create new thread for this question about ncurses/sbopkg: Is it possible to select a text displayed in ncurses dialog boxes - for example in README files displayed by sbopkg? Then it would be possible to create a queue file just by middleclick-pasteing dependencies from displayed README-s to a 'nano' editor on another konsole window.

If you're in X or have gpm running on a vt, you can hold shift while selecting and click to paste.

Thank you a lot for this tip! I didn't know that one.

There are several reasons:

1. I already provide a package on the sbopkg website (which includes the SlackBuild I use to create the package) so for me to create and maintain a SlackBuild script for sbopkg at SlackBuilds.org seems like a duplication of effort, IMHO (but, see #3).

2. I think it is important to keep a separation between SlackBuilds.org and sbopkg itself since SlackBuilds.org does not officially support or endorse sbopkg. Mentioning it in the FAQ might make some folks think the SlackBuilds.org admins provide support for sbopkg itself, and questions/bug reports to them would waste their time and not get to the right place (viz, the sbopkg team).

3. Notwithstanding #1, if someone thought it would be beneficial to have a sbopkg SlackBuild script at SlackBuilds.org, they are free to give it a go. However, nobody has created the script (or taken the one I provide) and submitted it to SlackBuilds.org. It might be the case that if someone else wanted to create and maintain a SlackBuild script for sbopkg in the SlackBuilds.org repo, it would be accepted.

ARCH is only set automatically if sbopkg finds that you are running x86_64. If you aren't then you can set it on the command line:

ARCH=i686 sbopkg

You could set it as an environmental variable, but that tends to give problems when compiling kernel modules.