On Thu, 18 Feb 2021, Ricardo J. Barberis wrote:
If you already use sbopkg to update your packages, you can also use it to
install new packages:
$ sudo sbopkg -i "package-name"
It won't install dependencies (you can use sqg as suggested elsewhere) but at
least you won't have to manually downloa
El Jueves 18/02/2021 a las 10:40, Rich Shepard escribió:
> On Thu, 18 Feb 2021, B Watson wrote:
> > You might want to use git to track changes to the repo.
>
> Every week after updates are posted I run sbopkg and update what's
> installed. Now I'm installing removed packages which is not automated
Does sync find packages I need that are not already installed? I was
under
the impression that when I ran sync it compared the SBo packages here
with
those on the SBo repo.
no, what it does is rsync your script repo with the public sbo (script)
repo, so all your sbo local slackbuild scrip
On Thu, 18 Feb 2021, Jeremy Hansen wrote:
All sbopkg's sync does is sync its local repo with SBo's online repo.
Jeremy,
I know that and have been using it that way for a long time.
However, since sbopkg itself doesn't track dependencies (that is kinda done
with sqg),
Aha! I knew there was
On Thu, Feb 18, 2021, 8:03 AM Rich Shepard wrote:
> On Thu, 18 Feb 2021, Tim Dickson via SlackBuilds-users wrote:
>
> > if you had run "sync" from within sbopkg as you just said, your
> > geoclue2.SlackBuild would have been the most up-to-date one, and you
> would
> > have avoided the problem you
On Wed, 17 Feb 2021, Jeremy Hansen wrote:
If you're going to build packages manually, it would probably be good to
keep a local git repo of SBo and update that before running SlackBuilds.
You can create the repo by running:
git clone git://git.slackbuilds.org/slackbuilds.git sbo-repo
Then you ca
On Thu, 18 Feb 2021, Tim Dickson via SlackBuilds-users wrote:
if you had run "sync" from within sbopkg as you just said, your
geoclue2.SlackBuild would have been the most up-to-date one, and you would
have avoided the problem you had, which makes it puzzling.
Tim,
Does sync find packages I n
see inline comment.
On 18/02/2021 13:40, Rich Shepard wrote:
On Thu, 18 Feb 2021, B Watson wrote:
*Please* try to avoid doing this. Before you send a mail to the list
asking for help with a problem, make sure the problem hasn't already
been fixed in the repo. We can't guess if you're using out
On Thu, 18 Feb 2021, B Watson wrote:
*Please* try to avoid doing this. Before you send a mail to the list
asking for help with a problem, make sure the problem hasn't already
been fixed in the repo. We can't guess if you're using outdated stuff
from 3 years ago, so we collectively wasted however
On Thu, 18 Feb 2021, at 3:28 PM, B Watson wrote:
> On 2/17/21, Rich Shepard wrote:
> >
> > The one that's been here since 2017 was modified in 2018 to include the
> > missing lines. I assumed that if the source tarballs were the same version
> > the build scripts would also be the same. That's bee
On 2/17/21, Rich Shepard wrote:
>
> The one that's been here since 2017 was modified in 2018 to include the
> missing lines. I assumed that if the source tarballs were the same version
> the build scripts would also be the same. That's been the case with other
> packages but now we know, not with
On Wed, Feb 17, 2021, 9:35 PM Rich Shepard wrote:
> On Wed, 17 Feb 2021, Jeremy Hansen wrote:
>
> > Those are taken directly from the SlackBuild script. It's how the script
> > determines whether or not to pass --disable-nmea-source to the configure
> > script.
>
> Jeremy,
>
> Thanks for pointing
On Wed, 17 Feb 2021, Jeremy Hansen wrote:
Those are taken directly from the SlackBuild script. It's how the script
determines whether or not to pass --disable-nmea-source to the configure
script.
Jeremy,
Thanks for pointing me to the problem and its solution.
When I went to rebuild geoclue2
13 matches
Mail list logo
