[sbopkg-users] Moving sbopkg to /usr/sbin and require root
Eric Schultz
eric at schultzter.ca
Fri Feb 10 17:33:21 UTC 2012
>
>
> 2012/2/10 Eric Schultz <eric at schultzter.ca>
>> 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.
>
>
> Except it should never have to write to the directory since my server is
>> taking care of keeping the local copy up-to-date.
>
>
> 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.
Good evening...
>
> --
> Ozan, BSc, BEng
Ah! I see, that answers that question then.
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.
Thanks,
<http://blog.schultzter.ca/p/about-me.html>
2012/2/10 <sbopkg-users-request at sbopkg.org>
> Send sbopkg-users mailing list submissions to
> sbopkg-users at sbopkg.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://sbopkg.org/mailman/listinfo/sbopkg-users
> or, via email, send a message with subject or body 'help' to
> sbopkg-users-request at sbopkg.org
>
> You can reach the person managing the list at
> sbopkg-users-owner at sbopkg.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sbopkg-users digest..."
>
> Today's Topics:
>
> 1. Re: Using http, Curl as a repository tool (slakmagik)
> 2. Re: Using http, Curl as a repository tool (Asaf)
> 3. Finding Help with GnuCash (jamesgilmour)
> 4. Re: Finding Help with GnuCash (Mauro Giachero)
> 5. Re: Finding Help with GnuCash (Pierre Cazenave)
> 6. Moving sbopkg to /usr/sbin and require root (Eric Schultz)
> 7. Re: Moving sbopkg to /usr/sbin and require root (Ozan T?rky?lmaz)
>
>
> ---------- Forwarded message ----------
> From: slakmagik <slakmagik at gmail.com>
> To: sbopkg-users at sbopkg.org
> Cc:
> Date: Wed, 3 Aug 2011 19:19:07 -0400
> Subject: Re: [sbopkg-users] Using http, Curl as a repository tool
> On 2011-08-03 (Wed) 23:18:21 [+0300], Asaf wrote:
> > Continued from:
> > http://sbopkg.org/pipermail/sbopkg-users/2010-July/000492.html
> >
> > I've forked sbopkg to implement Curl repository tool:
> > https://github.com/asafo/sbopkg
> >
> > there is also a sample repos.d/80-SBo-curl.repo
> >
> > I'll be happy for any suggestions to help it get merged
> >
>
> First, am I to understand that every use of 'sbopkg -r' using this would
> result in downloading the entire SBo repository? Because I don't think
> that's acceptable, both from a user's POV and from the SBo admin's POV.
>
> For less major points: your 80 repo file doesn't work because it
> attempts to sync to localhost. Even after correcting that to a full url,
> the protocol is duplicated in _curl_sync_package(). Even after
> correcting that, gunzip asks about whether it should overwrite
> SLACKBUILDS.TXT if that file already exists.
>
> For relatively minor points, we don't use the _func convention (not
> saying whether we should or not, but we don't) and your patches have
> trailing whitespace. Also we only use the '['-style test on pathnames
> and maybe not always then. We prefer '[[' for strings and '((' for
> numerics. We don't leave commented-out code in (if we do, it's a
> mistake). Error messages should announce that they're coming from
> $SCRIPT (and I don't mind even $FUNCNAME at times). While there's
> nothing in writing about and sbopkg is very bashistic, I'd personally
> still prefer to avoid stuff like BASH_REMATCH, though the use is really
> spiffy in this case and might well be the best thing to do. I'm not fond
> of _curl_fail() when it's only used once and its functionality could
> just be used directly in the _curl_sync_package() line where it's
> called. And I'm personally a <80 columns fanatic. Lines should fit
> within standard terminal widths wherever possible.
>
> Lastly, a major point, I'd raise first except that I wouldn't document
> something until I knew it was going in, myself, but anything that would
> go in would have to be thoroughly documented (man pages, always, and any
> relevant text files).
>
> Well, lastly lastly, I've only briefly looked at the patches (or patch,
> as it could be profitably 'squashed' into one, IMO) and only briefly
> tested but, while I'm testing, I'm noticing a lot of hangs and 'Curl
> Failed: 6's so this doesn't seem very efficient and effective even
> without the non-differencing problem.
>
> But, other than these points, it's pretty neat. I definitely appreciate
> your interest and this contribution but, if I understand it correctly, I
> don't think I'm in favor of it, at least at this point. We really do
> intend to get an lftp sync method in soon and, while that's not http, it
> might help with some people who have rsync issues while still only
> updating the differences. Or possibly something could be worked out via
> parsing the ChangeLog and only http'ing those packages.
>
> But maybe if Mauro's around, he'll have a different take.
>
> And, yeah, the http sync is still ongoing after having been started
> before I began this email (and I take forever with emails). ;)
>
>
>
> ---------- Forwarded message ----------
> From: Asaf <asaf at lingnu.com>
> To: sbopkg-users at sbopkg.org
> Cc:
> Date: Thu, 04 Aug 2011 10:32:49 +0300
> Subject: Re: [sbopkg-users] Using http, Curl as a repository tool
> On 08/04/2011 02:19 AM, slakmagik wrote:
>
>> On 2011-08-03 (Wed) 23:18:21 [+0300], Asaf wrote:
>>
>>> Continued from:
>>> http://sbopkg.org/pipermail/**sbopkg-users/2010-July/000492.**html<http://sbopkg.org/pipermail/sbopkg-users/2010-July/000492.html>
>>>
>>> I've forked sbopkg to implement Curl repository tool:
>>> https://github.com/asafo/**sbopkg <https://github.com/asafo/sbopkg>
>>>
>>> there is also a sample repos.d/80-SBo-curl.repo
>>>
>>> I'll be happy for any suggestions to help it get merged
>>>
>>> First, am I to understand that every use of 'sbopkg -r' using this would
>> result in downloading the entire SBo repository? Because I don't think
>> that's acceptable, both from a user's POV and from the SBo admin's POV.
>>
> Yes, the work is not complete yet, there are starting points for parsing
> the ChangeLog.txt file (Actually, the diff with the old ChangleLog.txt, if
> there is one)
> so that only new packages would get downloaded
>
> For less major points: your 80 repo file doesn't work because it
>> attempts to sync to localhost. Even after correcting that to a full url,
>> the protocol is duplicated in _curl_sync_package(). Even after
>> correcting that, gunzip asks about whether it should overwrite
>> SLACKBUILDS.TXT if that file already exists.
>>
> This is going to change, when ChangeLog.txt parsing implementation is
> complete,
> also, there is currently no public repository available (I hope that they
> will open one at
> slackbuilds.org), so I'm using localhost for testing
>
>>
>> For relatively minor points, we don't use the _func convention (not
>> saying whether we should or not, but we don't) and your patches have
>> trailing whitespace. Also we only use the '['-style test on pathnames
>> and maybe not always then. We prefer '[[' for strings and '((' for
>> numerics. We don't leave commented-out code in (if we do, it's a
>> mistake). Error messages should announce that they're coming from
>> $SCRIPT (and I don't mind even $FUNCNAME at times). While there's
>> nothing in writing about and sbopkg is very bashistic, I'd personally
>> still prefer to avoid stuff like BASH_REMATCH, though the use is really
>> spiffy in this case and might well be the best thing to do. I'm not fond
>> of _curl_fail() when it's only used once and its functionality could
>> just be used directly in the _curl_sync_package() line where it's
>> called. And I'm personally a<80 columns fanatic. Lines should fit
>> within standard terminal widths wherever possible.
>>
> the use of BASH_REMATCH saves a lot of process forking (grep, cut, sed,
> etc..)
> (or is there a third way ?)
>
>>
>> Lastly, a major point, I'd raise first except that I wouldn't document
>> something until I knew it was going in, myself, but anything that would
>> go in would have to be thoroughly documented (man pages, always, and any
>> relevant text files).
>>
>> Well, lastly lastly, I've only briefly looked at the patches (or patch,
>> as it could be profitably 'squashed' into one, IMO) and only briefly
>> tested but, while I'm testing, I'm noticing a lot of hangs and 'Curl
>> Failed: 6's so this doesn't seem very efficient and effective even
>> without the non-differencing problem.
>>
>> But, other than these points, it's pretty neat. I definitely appreciate
>> your interest and this contribution but, if I understand it correctly, I
>> don't think I'm in favor of it, at least at this point. We really do
>> intend to get an lftp sync method in soon and, while that's not http, it
>> might help with some people who have rsync issues while still only
>> updating the differences. Or possibly something could be worked out via
>> parsing the ChangeLog and only http'ing those packages.
>>
> lftp wouldn't solve the problem (restrictive firewalls)
>
>>
>> But maybe if Mauro's around, he'll have a different take.
>>
>> And, yeah, the http sync is still ongoing after having been started
>> before I began this email (and I take forever with emails). ;)
>> ______________________________**_________________
>> sbopkg-users mailing list
>> sbopkg-users at sbopkg.org
>> http://sbopkg.org/mailman/**listinfo/sbopkg-users<http://sbopkg.org/mailman/listinfo/sbopkg-users>
>>
>>
>
> --
> Asaf Ohaion
> Lingnu Open Source Consulting Ltd
> http://www.lingnu.com
>
>
>
>
> ---------- Forwarded message ----------
> From: jamesgilmour <jh-gilmour at bigpond.com>
> To: <sbopkg-users at sbopkg.org>
> Cc:
> Date: Wed, 19 Oct 2011 17:38:04 +1100
> Subject: [sbopkg-users] Finding Help with GnuCash
> Hi,
> I have downloaded GnuCash with sbopkg;when I try to open "Help"
> - Contents I get the error message '"help" not available, this
> is probably because "gnucash-docs" is not installed.'
> As 'GnuCash-docs' is not available in the sbopkg repository,
> what must I do to find it?
>
> --
> James&Helen
>
>
>
> ---------- Forwarded message ----------
> From: Mauro Giachero <mauro.giachero at gmail.com>
> To: Sbopkg Users List <sbopkg-users at sbopkg.org>
> Cc:
> Date: Wed, 19 Oct 2011 17:23:41 +0200
> Subject: Re: [sbopkg-users] Finding Help with GnuCash
> On Wed, Oct 19, 2011 at 08:38, jamesgilmour <jh-gilmour at bigpond.com>wrote:
>
>> Hi,
>>
>
> Hi
>
>
>> I have downloaded GnuCash with sbopkg;when I try to open "Help"
>> - Contents I get the error message '"help" not available, this
>> is probably because "gnucash-docs" is not installed.'
>> As 'GnuCash-docs' is not available in the sbopkg repository,
>> what must I do to find it?
>>
>
> 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.
>
> --
>> James&Helen
>>
>
> [1] http://slackbuilds.org/repository/13.37/business/gnucash/
>
> Regards
> --
> Mauro Giachero
>
>
> ---------- Forwarded message ----------
> From: Pierre Cazenave <pwcazenave at gmail.com>
> To: Sbopkg Users List <sbopkg-users at sbopkg.org>
> Cc:
> Date: Wed, 19 Oct 2011 17:15:09 +0100
> Subject: Re: [sbopkg-users] Finding Help with GnuCash
>
>
> On 19/10/2011 07:38, jamesgilmour wrote:
>
>> Hi,
>> I have downloaded GnuCash with sbopkg;when I try to open "Help"
>> - Contents I get the error message '"help" not available, this
>> is probably because "gnucash-docs" is not installed.'
>> As 'GnuCash-docs' is not available in the sbopkg repository,
>> what must I do to find it?
>>
>>
> Either someone will have to submit a script to build it [0], or you can
> use the online version:
>
> http://code.gnucash.org/docs/**help/help.html<http://code.gnucash.org/docs/help/help.html>
>
> Pierre
>
> [0] http://sourceforge.net/**projects/gnucash/files/**gnucash-docs/2.4.1/<http://sourceforge.net/projects/gnucash/files/gnucash-docs/2.4.1/>
>
>
>
> ---------- Forwarded message ----------
> From: Eric Schultz <eric at schultzter.ca>
> To: sbopkg-users at sbopkg.org
> Cc:
> Date: Fri, 10 Feb 2012 00:39:20 -0500
> Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root
> Good evening...
>
> Sorry to re-open an old and probably closed discussion but I have a
> pertinent situation.
>
> 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.
>
> 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.
>
> 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.
>
> Except it should never have to write to the directory since my server is
> taking care of keeping the local copy up-to-date.
>
> 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?
>
> Thanks,
>
> BTW, is there a searchable archive for sbopkg-users? I couldn't find
> anything on gmane or marc.
>
> <http://blog.schultzter.ca/p/about-me.html>
>
>
>
> ---------- Forwarded message ----------
> From: "Ozan Türkyılmaz" <ozan.turkyilmaz at gmail.com>
> To: Sbopkg Users List <sbopkg-users at sbopkg.org>
> Cc:
> Date: Fri, 10 Feb 2012 10:56:17 +0500
> Subject: Re: [sbopkg-users] Moving sbopkg to /usr/sbin and require root
> 2012/2/10 Eric Schultz <eric at schultzter.ca>
>
>> Good evening...
>>
>> 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.
>>
>> Except it should never have to write to the directory since my server is
>> taking care of keeping the local copy up-to-date.
>>
>
> 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.
>
>
> --
> Ozan, BSc, BEng
>
>
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20120210/fc1152e5/attachment-0001.html>
More information about the sbopkg-users
mailing list