<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br style><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
2012/2/10 Eric Schultz <span dir="ltr"><<a href="mailto:eric@schultzter.ca" target="_blank" style="color:rgb(17,85,204)">eric@schultzter.ca</a>><br></span>But sbopkg is checking to see if it has write-access to the directory, which it doesn't. Normally root won't on an NFS mounted share (security/paranoia, that kind of thing). So it fails, right from the start.</blockquote>
</blockquote><div> </div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Except it should never have to write to the directory since my server is taking care of keeping the local copy up-to-date.</blockquote>
</blockquote><div> </div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
sbopkg creates a syslink from source tarball in cache folder to the folder where the script is (in the repo). That's where it needs write access in the first place and secondly Bild sciprt itself may need it as well for some reason.</blockquote>
<div class="gmail_quote" style><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Good evening...<br></blockquote></div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br style><span style>-- <br></span><span style>Ozan, BSc, BEng</span></blockquote><div><br></div><div>Ah! I see, that answers that question then.</div><div><br></div><div>I guess what I can do is sync SBo to my NAS and then sync my computers from there. Although I was considering using ponce's -current repository (since I just upgraded to -current) and that requires git, which my NAS doesn't do.</div>
<div><br></div><div>Thanks,</div><div><br></div><div><a href="http://blog.schultzter.ca/p/about-me.html" target="_blank"><img src="http://lh5.ggpht.com/_yN15t6Lk3OU/TLRxe5yRnkI/AAAAAAAAJTg/dnEFclbZCN8/s800/weemee-signature-s.jpg"></a></div>
<br>
<br><br><div class="gmail_quote">2012/2/10 <span dir="ltr"><<a href="mailto:sbopkg-users-request@sbopkg.org">sbopkg-users-request@sbopkg.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send sbopkg-users mailing list submissions to<br>
<a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://sbopkg.org/mailman/listinfo/sbopkg-users" target="_blank">http://sbopkg.org/mailman/listinfo/sbopkg-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sbopkg-users-request@sbopkg.org">sbopkg-users-request@sbopkg.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sbopkg-users-owner@sbopkg.org">sbopkg-users-owner@sbopkg.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of sbopkg-users digest..."<br>
<br>Today's Topics:<br>
<br>
1. Re: Using http, Curl as a repository tool (slakmagik)<br>
2. Re: Using http, Curl as a repository tool (Asaf)<br>
3. Finding Help with GnuCash (jamesgilmour)<br>
4. Re: Finding Help with GnuCash (Mauro Giachero)<br>
5. Re: Finding Help with GnuCash (Pierre Cazenave)<br>
6. Moving sbopkg to /usr/sbin and require root (Eric Schultz)<br>
7. Re: Moving sbopkg to /usr/sbin and require root (Ozan T?rky?lmaz)<br>
<br><br>---------- Forwarded message ----------<br>From: slakmagik <<a href="mailto:slakmagik@gmail.com">slakmagik@gmail.com</a>><br>To: <a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a><br>Cc: <br>
Date: Wed, 3 Aug 2011 19:19:07 -0400<br>Subject: Re: [sbopkg-users] Using http, Curl as a repository tool<br>On 2011-08-03 (Wed) 23:18:21 [+0300], Asaf wrote:<br>
> Continued from:<br>
> <a href="http://sbopkg.org/pipermail/sbopkg-users/2010-July/000492.html" target="_blank">http://sbopkg.org/pipermail/sbopkg-users/2010-July/000492.html</a><br>
><br>
> I've forked sbopkg to implement Curl repository tool:<br>
> <a href="https://github.com/asafo/sbopkg" target="_blank">https://github.com/asafo/sbopkg</a><br>
><br>
> there is also a sample repos.d/80-SBo-curl.repo<br>
><br>
> I'll be happy for any suggestions to help it get merged<br>
><br>
<br>
First, am I to understand that every use of 'sbopkg -r' using this would<br>
result in downloading the entire SBo repository? Because I don't think<br>
that's acceptable, both from a user's POV and from the SBo admin's POV.<br>
<br>
For less major points: your 80 repo file doesn't work because it<br>
attempts to sync to localhost. Even after correcting that to a full url,<br>
the protocol is duplicated in _curl_sync_package(). Even after<br>
correcting that, gunzip asks about whether it should overwrite<br>
SLACKBUILDS.TXT if that file already exists.<br>
<br>
For relatively minor points, we don't use the _func convention (not<br>
saying whether we should or not, but we don't) and your patches have<br>
trailing whitespace. Also we only use the '['-style test on pathnames<br>
and maybe not always then. We prefer '[[' for strings and '((' for<br>
numerics. We don't leave commented-out code in (if we do, it's a<br>
mistake). Error messages should announce that they're coming from<br>
$SCRIPT (and I don't mind even $FUNCNAME at times). While there's<br>
nothing in writing about and sbopkg is very bashistic, I'd personally<br>
still prefer to avoid stuff like BASH_REMATCH, though the use is really<br>
spiffy in this case and might well be the best thing to do. I'm not fond<br>
of _curl_fail() when it's only used once and its functionality could<br>
just be used directly in the _curl_sync_package() line where it's<br>
called. And I'm personally a <80 columns fanatic. Lines should fit<br>
within standard terminal widths wherever possible.<br>
<br>
Lastly, a major point, I'd raise first except that I wouldn't document<br>
something until I knew it was going in, myself, but anything that would<br>
go in would have to be thoroughly documented (man pages, always, and any<br>
relevant text files).<br>
<br>
Well, lastly lastly, I've only briefly looked at the patches (or patch,<br>
as it could be profitably 'squashed' into one, IMO) and only briefly<br>
tested but, while I'm testing, I'm noticing a lot of hangs and 'Curl<br>
Failed: 6's so this doesn't seem very efficient and effective even<br>
without the non-differencing problem.<br>
<br>
But, other than these points, it's pretty neat. I definitely appreciate<br>
your interest and this contribution but, if I understand it correctly, I<br>
don't think I'm in favor of it, at least at this point. We really do<br>
intend to get an lftp sync method in soon and, while that's not http, it<br>
might help with some people who have rsync issues while still only<br>
updating the differences. Or possibly something could be worked out via<br>
parsing the ChangeLog and only http'ing those packages.<br>
<br>
But maybe if Mauro's around, he'll have a different take.<br>
<br>
And, yeah, the http sync is still ongoing after having been started<br>
before I began this email (and I take forever with emails). ;)<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: Asaf <<a href="mailto:asaf@lingnu.com">asaf@lingnu.com</a>><br>To: <a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a><br>Cc: <br>Date: Thu, 04 Aug 2011 10:32:49 +0300<br>
Subject: Re: [sbopkg-users] Using http, Curl as a repository tool<br>On 08/04/2011 02:19 AM, slakmagik wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2011-08-03 (Wed) 23:18:21 [+0300], Asaf wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Continued from:<br>
<a href="http://sbopkg.org/pipermail/sbopkg-users/2010-July/000492.html" target="_blank">http://sbopkg.org/pipermail/<u></u>sbopkg-users/2010-July/000492.<u></u>html</a><br>
<br>
I've forked sbopkg to implement Curl repository tool:<br>
<a href="https://github.com/asafo/sbopkg" target="_blank">https://github.com/asafo/<u></u>sbopkg</a><br>
<br>
there is also a sample repos.d/80-SBo-curl.repo<br>
<br>
I'll be happy for any suggestions to help it get merged<br>
<br>
</blockquote>
First, am I to understand that every use of 'sbopkg -r' using this would<br>
result in downloading the entire SBo repository? Because I don't think<br>
that's acceptable, both from a user's POV and from the SBo admin's POV.<br>
</blockquote>
Yes, the work is not complete yet, there are starting points for parsing<br>
the ChangeLog.txt file (Actually, the diff with the old ChangleLog.txt, if there is one)<br>
so that only new packages would get downloaded<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For less major points: your 80 repo file doesn't work because it<br>
attempts to sync to localhost. Even after correcting that to a full url,<br>
the protocol is duplicated in _curl_sync_package(). Even after<br>
correcting that, gunzip asks about whether it should overwrite<br>
SLACKBUILDS.TXT if that file already exists.<br>
</blockquote>
This is going to change, when ChangeLog.txt parsing implementation is complete,<br>
also, there is currently no public repository available (I hope that they will open one at<br>
<a href="http://slackbuilds.org" target="_blank">slackbuilds.org</a>), so I'm using localhost for testing<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For relatively minor points, we don't use the _func convention (not<br>
saying whether we should or not, but we don't) and your patches have<br>
trailing whitespace. Also we only use the '['-style test on pathnames<br>
and maybe not always then. We prefer '[[' for strings and '((' for<br>
numerics. We don't leave commented-out code in (if we do, it's a<br>
mistake). Error messages should announce that they're coming from<br>
$SCRIPT (and I don't mind even $FUNCNAME at times). While there's<br>
nothing in writing about and sbopkg is very bashistic, I'd personally<br>
still prefer to avoid stuff like BASH_REMATCH, though the use is really<br>
spiffy in this case and might well be the best thing to do. I'm not fond<br>
of _curl_fail() when it's only used once and its functionality could<br>
just be used directly in the _curl_sync_package() line where it's<br>
called. And I'm personally a<80 columns fanatic. Lines should fit<br>
within standard terminal widths wherever possible.<br>
</blockquote>
the use of BASH_REMATCH saves a lot of process forking (grep, cut, sed, etc..)<br>
(or is there a third way ?)<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Lastly, a major point, I'd raise first except that I wouldn't document<br>
something until I knew it was going in, myself, but anything that would<br>
go in would have to be thoroughly documented (man pages, always, and any<br>
relevant text files).<br>
<br>
Well, lastly lastly, I've only briefly looked at the patches (or patch,<br>
as it could be profitably 'squashed' into one, IMO) and only briefly<br>
tested but, while I'm testing, I'm noticing a lot of hangs and 'Curl<br>
Failed: 6's so this doesn't seem very efficient and effective even<br>
without the non-differencing problem.<br>
<br>
But, other than these points, it's pretty neat. I definitely appreciate<br>
your interest and this contribution but, if I understand it correctly, I<br>
don't think I'm in favor of it, at least at this point. We really do<br>
intend to get an lftp sync method in soon and, while that's not http, it<br>
might help with some people who have rsync issues while still only<br>
updating the differences. Or possibly something could be worked out via<br>
parsing the ChangeLog and only http'ing those packages.<br>
</blockquote>
lftp wouldn't solve the problem (restrictive firewalls)<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
But maybe if Mauro's around, he'll have a different take.<br>
<br>
And, yeah, the http sync is still ongoing after having been started<br>
before I began this email (and I take forever with emails). ;)<br>
______________________________<u></u>_________________<br>
sbopkg-users mailing list<br>
<a href="mailto:sbopkg-users@sbopkg.org" target="_blank">sbopkg-users@sbopkg.org</a><br>
<a href="http://sbopkg.org/mailman/listinfo/sbopkg-users" target="_blank">http://sbopkg.org/mailman/<u></u>listinfo/sbopkg-users</a><br>
<br>
</blockquote>
<br>
<br>
-- <br>
Asaf Ohaion<br>
Lingnu Open Source Consulting Ltd<br>
<a href="http://www.lingnu.com" target="_blank">http://www.lingnu.com</a><br>
<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: jamesgilmour <<a href="mailto:jh-gilmour@bigpond.com">jh-gilmour@bigpond.com</a>><br>To: <<a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a>><br>
Cc: <br>Date: Wed, 19 Oct 2011 17:38:04 +1100<br>Subject: [sbopkg-users] Finding Help with GnuCash<br> Hi,<br>
I have downloaded GnuCash with sbopkg;when I try to open "Help"<br>
- Contents I get the error message '"help" not available, this<br>
is probably because "gnucash-docs" is not installed.'<br>
As 'GnuCash-docs' is not available in the sbopkg repository,<br>
what must I do to find it?<br>
<br>
--<br>
James&Helen<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: Mauro Giachero <<a href="mailto:mauro.giachero@gmail.com">mauro.giachero@gmail.com</a>><br>To: Sbopkg Users List <<a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a>><br>
Cc: <br>Date: Wed, 19 Oct 2011 17:23:41 +0200<br>Subject: Re: [sbopkg-users] Finding Help with GnuCash<br><div class="gmail_quote">On Wed, Oct 19, 2011 at 08:38, jamesgilmour <span dir="ltr"><<a href="mailto:jh-gilmour@bigpond.com" target="_blank">jh-gilmour@bigpond.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br></blockquote><div><br>Hi<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I have downloaded GnuCash with sbopkg;when I try to open "Help"<br>
- Contents I get the error message '"help" not available, this<br>
is probably because "gnucash-docs" is not installed.'<br>
As 'GnuCash-docs' is not available in the sbopkg repository,<br>
what must I do to find it?<br></blockquote><div><br>You should ask to the gnucash maintainer (his mail is available in the gnucash page on SBo, see [1]). Your problem is very gnucash-specific, and sbopkg doesn't know much about the packages it builds. <br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font color="#888888">
--<br>
James&Helen</font><br></blockquote><div><br>[1] <a href="http://slackbuilds.org/repository/13.37/business/gnucash/" target="_blank">http://slackbuilds.org/repository/13.37/business/gnucash/</a><br></div></div><br>Regards<br>
-- <br>Mauro Giachero<br>
<br><br>---------- Forwarded message ----------<br>From: Pierre Cazenave <<a href="mailto:pwcazenave@gmail.com">pwcazenave@gmail.com</a>><br>To: Sbopkg Users List <<a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a>><br>
Cc: <br>Date: Wed, 19 Oct 2011 17:15:09 +0100<br>Subject: Re: [sbopkg-users] Finding Help with GnuCash<br><br>
<br>
On 19/10/2011 07:38, jamesgilmour wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
I have downloaded GnuCash with sbopkg;when I try to open "Help"<br>
- Contents I get the error message '"help" not available, this<br>
is probably because "gnucash-docs" is not installed.'<br>
As 'GnuCash-docs' is not available in the sbopkg repository,<br>
what must I do to find it?<br>
<br>
</blockquote>
<br>
Either someone will have to submit a script to build it [0], or you can use the online version:<br>
<br>
<a href="http://code.gnucash.org/docs/help/help.html" target="_blank">http://code.gnucash.org/docs/<u></u>help/help.html</a><br>
<br>
Pierre<br>
<br>
[0] <a href="http://sourceforge.net/projects/gnucash/files/gnucash-docs/2.4.1/" target="_blank">http://sourceforge.net/<u></u>projects/gnucash/files/<u></u>gnucash-docs/2.4.1/</a><br>
<br>
<br><br>---------- Forwarded message ----------<br>From: Eric Schultz <<a href="mailto:eric@schultzter.ca">eric@schultzter.ca</a>><br>To: <a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a><br>Cc: <br>
Date: Fri, 10 Feb 2012 00:39:20 -0500<br>Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root<br>Good evening...<div><br></div><div>Sorry to re-open an old and probably closed discussion but I have a pertinent situation.</div>
<div><br></div><div>Perhaps there's something I'm not understanding, but I want to do is have my server (a NAS) rsync the SlackBuilds.org repository so it's available to all my computers. Rather than have each one sync the repository themselves. I know it's not much data but it seems much more efficient to only do it once.</div>
<div><br></div><div>As such, I wanted to set the REPO_ROOT to an NFS mounted directory from my server. And of course the REPO_NAME and REPO_BRANCH appropriately too.</div><div><br></div><div>But sbopkg is checking to see if it has write-access to the directory, which it doesn't. Normally root won't on an NFS mounted share (security/paranoia, that kind of thing). So it fails, right from the start.</div>
<div><br></div><div>Except it should never have to write to the directory since my server is taking care of keeping the local copy up-to-date.</div><div><br></div><div>I've done some bash scripting, so I could probably contribute but is this already possible with some option I've missed? Or is there some "gotcha" that will make this difficult or impossible to implement?</div>
<div><br></div><div>Thanks,</div><div><br></div><div>BTW, is there a searchable archive for sbopkg-users? I couldn't find anything on gmane or marc.</div><div><br></div><div><div><a href="http://blog.schultzter.ca/p/about-me.html" target="_blank"><img></a></div>
<br>
</div>
<br><br>---------- Forwarded message ----------<br>From: "Ozan Türkyılmaz" <<a href="mailto:ozan.turkyilmaz@gmail.com">ozan.turkyilmaz@gmail.com</a>><br>To: Sbopkg Users List <<a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a>><br>
Cc: <br>Date: Fri, 10 Feb 2012 10:56:17 +0500<br>Subject: Re: [sbopkg-users] Moving sbopkg to /usr/sbin and require root<br><div class="gmail_quote">2012/2/10 Eric Schultz <span dir="ltr"><<a href="mailto:eric@schultzter.ca" target="_blank">eric@schultzter.ca</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Good evening...<div><br></div>But sbopkg is checking to see if it has write-access to the directory, which it doesn't. Normally root won't on an NFS mounted share (security/paranoia, that kind of thing). So it fails, right from the start.
<div><br></div><div>Except it should never have to write to the directory since my server is taking care of keeping the local copy up-to-date.</div></blockquote><div><br>sbopkg creates a syslink from source tarball in cache folder to the folder where the script is (in the repo). That's where it needs write access in the first place and secondly Bild sciprt itself may need it as well for some reason.<br>
</div></div><br clear="all"><br>-- <br>Ozan, BSc, BEng<br><br>
<br>_______________________________________________<br>
sbopkg-users mailing list<br>
<a href="mailto:sbopkg-users@sbopkg.org">sbopkg-users@sbopkg.org</a><br>
<a href="http://sbopkg.org/mailman/listinfo/sbopkg-users" target="_blank">http://sbopkg.org/mailman/listinfo/sbopkg-users</a><br>
<br></blockquote></div><br>