From rworkman at slackbuilds.org  Wed Feb 18 16:39:06 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 18 Feb 2009 10:39:06 -0600
Subject: [Sbopkg-users] Test Message
Message-ID: <20090218103906.0774e282@liberty.rlwhome.lan>

This is just a test. 

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090218/08a718e7/attachment.asc>

From chess at sbopkg.org  Wed Feb 18 20:20:03 2009
From: chess at sbopkg.org (Chess Griffin)
Date: Wed, 18 Feb 2009 15:20:03 -0500
Subject: [Sbopkg-users] Another test
Message-ID: <499C6D73.8090509@sbopkg.org>

Test to ML.

-- 
Chess Griffin

From rworkman at slackbuilds.org  Wed Feb 18 20:42:32 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 18 Feb 2009 14:42:32 -0600
Subject: [Sbopkg-users] Another test
In-Reply-To: <499C6D73.8090509@sbopkg.org>
References: <499C6D73.8090509@sbopkg.org>
Message-ID: <20090218144232.415d6851@liberty.rlwhome.lan>

On Wed, 18 Feb 2009 15:20:03 -0500
Chess Griffin <chess at sbopkg.org> wrote:

> Test to ML.
> 

Confirmed that it works here, and I'm replying to make sure that my
Mailman upgrade to 2.1.12rc2 went okay.  :-)

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090218/4d354816/attachment.asc>

From chess at chessgriffin.com  Wed Feb 18 14:20:57 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 18 Feb 2009 09:20:57 -0500
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <da3e877f0902180103t667587c5n55a73df088c7242b@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com> <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com> <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com> <da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com> <20090217232346.GC4322@localhost> <eded84250902172129t3f2480a0n2f51a76189d0a629@mail.gmail.com> <da3e877f0902180103t667587c5n55a73df088c7242b@mail.gmail.com>
Message-ID: <20090218142057.GA4461@localhost>

* Mauro Giachero <mauro.giachero at gmail.com> [2009-02-18 10:03:08]:

> On Wed, Feb 18, 2009 at 6:29 AM, Phillip Warner
> <phillip.c.warner at gmail.com>wrote:
> 
> > [...]
> > Did y'all mean that you don't want the Local/Original/Diff Dialog to
> > show up if the files are the same?
> 
> 
> Exactly. Sorry if I used a bad wording.

Yes, that was the current behavior which is preferable.

> 
> 
> > If that is the case, then instead
> > of using a tmp file why not have a statement similar to this
> >
> > if [ -n "$(diff -q file1 file2 2>/dev/null)" ]; then
> >  # do_dialog_code
> > fi
> >
> > This would keep y'all from having to manage even more tmp files.
> 
> 
> But this would to the diff twice...
> I really think it's a matter of taste here. Frankly, I'm not worried about
> temp files whose lifespan doesn't exceed that of a single function -- after
> all, it's rather easy to manage them correctly.
> 

I agree.  Let's go with Mauro's patch that leaves the tmp file and includes
the DIFF and DIFFOPTS variables.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090218/850ece99/attachment.sig>

From mauro.giachero at gmail.com  Wed Feb 18 09:03:08 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 18 Feb 2009 10:03:08 +0100
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <eded84250902172129t3f2480a0n2f51a76189d0a629@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com> <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com> <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com> <da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com> <20090217232346.GC4322@localhost> <eded84250902172129t3f2480a0n2f51a76189d0a629@mail.gmail.com>
Message-ID: <da3e877f0902180103t667587c5n55a73df088c7242b@mail.gmail.com>

On Wed, Feb 18, 2009 at 6:29 AM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:

> [...]
> Did y'all mean that you don't want the Local/Original/Diff Dialog to
> show up if the files are the same?


Exactly. Sorry if I used a bad wording.


> If that is the case, then instead
> of using a tmp file why not have a statement similar to this
>
> if [ -n "$(diff -q file1 file2 2>/dev/null)" ]; then
>  # do_dialog_code
> fi
>
> This would keep y'all from having to manage even more tmp files.


But this would to the diff twice...
I really think it's a matter of taste here. Frankly, I'm not worried about
temp files whose lifespan doesn't exceed that of a single function -- after
all, it's rather easy to manage them correctly.

-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090218/3cf43a78/attachment.htm>

From phillip.c.warner at gmail.com  Wed Feb 18 05:29:35 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Tue, 17 Feb 2009 23:29:35 -0600
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <20090217232346.GC4322@localhost>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com> <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com> <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com> <da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com> <20090217232346.GC4322@localhost>
Message-ID: <eded84250902172129t3f2480a0n2f51a76189d0a629@mail.gmail.com>


On 2/17/09, Chess Griffin <chess at chessgriffin.com> wrote:
> I prefer keeping the temp file for the reason Mauro mentioned in
> addition to being able to view it more than once.
You can still view it more than once, but it diffs everytime.  These
files are small so it's not like there is a performance hit, and how
many times are people going to hit 'Diff' over and over again.  Do you
mean open another *term and view the tmp file itself?

What dialog does not show up?  When I test it I choose the diff option
and the diff dialog with the title and OK button shows up.  Of course
there is nothing in the dialog, but that is simply because there are
no differences to show.  This could be made less confusing
(particularly for the non-dialog version) by making the default
DIFFOPS=-su.

Did y'all mean that you don't want the Local/Original/Diff Dialog to
show up if the files are the same?  If that is the case, then instead
of using a tmp file why not have a statement similar to this

if [ -n "$(diff -q file1 file2 2>/dev/null)" ]; then
  # do_dialog_code
fi

This would keep y'all from having to manage even more tmp files.

> Honestly, I am not
> sure if $DIFF and $DIFFOPTS are really needed -- the idea here is just
> to provide a simple means of showing a diff.  We're only showing
> differences between .info and the SlackBuild scripts, so isn't diff -u
> sufficient?
Some people don't care about spacing.  Some like unified diffs, and
others like standard.  Maybe someone wants to use colordiff instead of
diff itself (for non dialog).  I just thought it would be nice to have
these options.  You could define the vars at the top so the code is
simpler.

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Tue Feb 17 23:23:47 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 17 Feb 2009 18:23:47 -0500
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com> <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com> <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com> <da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com>
Message-ID: <20090217232346.GC4322@localhost>

* Mauro Giachero <mauro.giachero at gmail.com> [2009-02-17 11:02:56]:

> On Tue, Feb 17, 2009 at 1:12 AM, Phillip Warner
> <phillip.c.warner at gmail.com>wrote:
> 
> > here is my patch for rev 457
> >
> > I took out the tmp file, added the DIFF and DIFFOPS, and made some
> > other minor adjustments.
> 
> 
> Thank you for the patch. I'll let Chess pick this up.
> Anyway, the fact that you dropped the tmp causes a (minor) regression: as it
> stands before the patch, if the local and original file are equal, the
> dialog doesn't show up.
> So I'd rather pick up the attached one (untested).
> (Chess, either way we should document the new DIFF and DIFFOPTS variables).
> 

I prefer keeping the temp file for the reason Mauro mentioned in
addition to being able to view it more than once.  Honestly, I am not
sure if $DIFF and $DIFFOPTS are really needed -- the idea here is just
to provide a simple means of showing a diff.  We're only showing
differences between .info and the SlackBuild scripts, so isn't diff -u
sufficient?

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/e692cbd7/attachment.sig>

From mauro.giachero at gmail.com  Tue Feb 17 10:02:56 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Tue, 17 Feb 2009 11:02:56 +0100
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com> <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com> <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com>
Message-ID: <da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com>

On Tue, Feb 17, 2009 at 1:12 AM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:

> here is my patch for rev 457
>
> I took out the tmp file, added the DIFF and DIFFOPS, and made some
> other minor adjustments.


Thank you for the patch. I'll let Chess pick this up.
Anyway, the fact that you dropped the tmp causes a (minor) regression: as it
stands before the patch, if the local and original file are equal, the
dialog doesn't show up.
So I'd rather pick up the attached one (untested).
(Chess, either way we should document the new DIFF and DIFFOPTS variables).

Comments?
-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/9258a625/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbopkg-diffs-mg.patch
Type: text/x-diff
Size: 2434 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/9258a625/attachment.bin>

From phillip.c.warner at gmail.com  Tue Feb 17 00:12:30 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 18:12:30 -0600
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com> <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com>
Message-ID: <eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com>

here is my patch for rev 457

I took out the tmp file, added the DIFF and DIFFOPS, and made some
other minor adjustments.

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbopkg-diffs.patch
Type: application/octet-stream
Size: 3687 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/45f3effa/attachment.obj>

From phillip.c.warner at gmail.com  Mon Feb 16 23:18:09 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 17:18:09 -0600
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com> <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com>
Message-ID: <eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com>


I started using sspm, so now I am up to date with SVN.

Do we really need a tmp file for the diff itself?  One major
difference between the patches is that my implementation creates the
diff only when it is called upon.  The only disadvantage to this would
be if someone wante to view the diff over and over again.  The
advantage is that you don't have to have all of these lines cleaning
up the tmp file.

I'll add the DIFF and DIFFOPS in and see what else can be merged.

Perhaps I should get on IRC...

--phillip

On 2/16/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> On Mon, Feb 16, 2009 at 4:05 PM, Phillip Warner
> <phillip.c.warner at gmail.com>wrote:
>
>> > * shadowsnipes <phillip.c.warner at gmail.com> [2009-01-29 18:24:21]:
>> >>
>> >> When you choose to build a package a dialog pops up if you have
>> >> customized the SlackBuild.  You are asked whether or not to use your
>> >> custom .SlackBuild file or the official repo file.  A good third
>> >> option would be to show a diff of the two (and then return back to
>> >> that dialog after done viewing).
>>
>> Attached is a patch that implements this.  Note that you can define
>> the DIFF program to use and DIFFOPS (diff options).  DIFF is useful in
>> case, for instance, you want to use colordiff in the non-dialog
>> output.
>>
>> When I get a chance I'll implement the diffs for the previous
>> SlackBuild versions as mentioned in the second part of the original
>> post.
>>
>> --phillip
>>
>
> Thank you, but I'm afraid that an implementation of this is has already been
> done by Chess (see SVN revision 444, with some fixes till 449).
>
> I see there are some differences between the two (at least the $DIFF and
> $DIFFOPTS, but I don't know if there are others relevant). Would you mind to
> apply your improvements on top of the current SVN head (function pick_file)?
> This way it'll be far easier for us to merge it.
>
> For the future, I recommend to grab the latest SVN revision to do
> development. Sometimes there are big differences between the last stable
> release and the SVN tip...
>
> With best regards, and many thanks for your efforts in improving sbopkg
> --
> Mauro Giachero
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From mauro.giachero at gmail.com  Mon Feb 16 15:21:02 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Mon, 16 Feb 2009 16:21:02 +0100
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost> <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com>
Message-ID: <da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com>

On Mon, Feb 16, 2009 at 4:05 PM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:

> > * shadowsnipes <phillip.c.warner at gmail.com> [2009-01-29 18:24:21]:
> >>
> >> When you choose to build a package a dialog pops up if you have
> >> customized the SlackBuild.  You are asked whether or not to use your
> >> custom .SlackBuild file or the official repo file.  A good third
> >> option would be to show a diff of the two (and then return back to
> >> that dialog after done viewing).
>
> Attached is a patch that implements this.  Note that you can define
> the DIFF program to use and DIFFOPS (diff options).  DIFF is useful in
> case, for instance, you want to use colordiff in the non-dialog
> output.
>
> When I get a chance I'll implement the diffs for the previous
> SlackBuild versions as mentioned in the second part of the original
> post.
>
> --phillip
>

Thank you, but I'm afraid that an implementation of this is has already been
done by Chess (see SVN revision 444, with some fixes till 449).

I see there are some differences between the two (at least the $DIFF and
$DIFFOPTS, but I don't know if there are others relevant). Would you mind to
apply your improvements on top of the current SVN head (function pick_file)?
This way it'll be far easier for us to merge it.

For the future, I recommend to grab the latest SVN revision to do
development. Sometimes there are big differences between the last stable
release and the SVN tip...

With best regards, and many thanks for your efforts in improving sbopkg
-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/1daa83af/attachment.htm>

From phillip.c.warner at gmail.com  Mon Feb 16 15:05:14 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 09:05:14 -0600
Subject: [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <20090130040836.GD11406@localhost>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com> <20090130040836.GD11406@localhost>
Message-ID: <eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com>

On 1/29/09, Chess Griffin <chess at chessgriffin.com> wrote:
> * shadowsnipes <phillip.c.warner at gmail.com> [2009-01-29 18:24:21]:
>
>>
>> When you choose to build a package a dialog pops up if you have
>> customized the SlackBuild.  You are asked whether or not to use your
>> custom .SlackBuild file or the official repo file.  A good third
>> option would be to show a diff of the two (and then return back to
>> that dialog after done viewing).
>
> Not a bad idea.  I'll put this on the TODO.  :-)
>
Attached is a patch that implements this.  Note that you can define
the DIFF program to use and DIFFOPS (diff options).  DIFF is useful in
case, for instance, you want to use colordiff in the non-dialog
output.

When I get a chance I'll implement the diffs for the previous
SlackBuild versions as mentioned in the second part of the original
post.

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
A non-text attachment was scrubbed...
Name: file_diffs-0.26.2.patch
Type: application/octet-stream
Size: 5448 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/6b29875f/attachment.obj>

From xma at gnu.org  Tue Feb  3 12:19:55 2009
From: xma at gnu.org (xma at gnu.org)
Date: Tue, 03 Feb 2009 13:19:55 +0100
Subject: [sbopkg-discuss] Re: Feature request - test build option
In-Reply-To: <c4eba0cf-bfd5-4b6e-821f-19b3af00f6a8@f20g2000yqg.googlegroups.com>
References: <c4eba0cf-bfd5-4b6e-821f-19b3af00f6a8@f20g2000yqg.googlegroups.com>
Message-ID: <20660.1233663595@zogzog.maillard.mobi>


I think this idea is great !

Regards

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Mon Feb  2 18:38:44 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 2 Feb 2009 13:38:44 -0500
Subject: [sbopkg-discuss] Re: source?
In-Reply-To: <2d5309d0-8a3e-4aa3-88fb-af2e010a384c@t39g2000prh.googlegroups.com>
References: <278c9aa8-8d6d-4018-a101-3c01c62e915a@40g2000prx.googlegroups.com> <20090201191744.2acf416f@liberty.rlwhome.lan> <20090202034726.GA26756@localhost> <2d5309d0-8a3e-4aa3-88fb-af2e010a384c@t39g2000prh.googlegroups.com>
Message-ID: <20090202183843.GA18745@localhost>

* dchmelik at gmail.com <dchmelik at hipplanet.com> [2009-02-02 06:13:13]:

> I should have realized it was a script (I have seen few that do as
> much as compiled programs that are usually larger, and I still think
> of .BATs)... it is long for a script; I should learn to code sh like
> that.  Some Slamd64 software is recommended to be compiled with
> slackbuilds (and maybe a couple modifications;) some are even in the
> distro: will sbopkg not compile stuff with it?

SlackBuilds are shell scripts that compile source into Slackware
packages.  Patrick Volkerding uses SlackBuild scripts to create the
official packages.  If you browse any of the Slackware mirrors
and look in the /source directory, you'll see all the sources and
the accompanying SlackBuild script used by Patrick.

SlackBuilds.org is a community-run site that maintains user-contributed
SlackBuilds for third-party software not included in official Slackware.
Sbopkg is a 'front-end' to SlackBuilds.org.  Sbopkg will perform an
rsync of the SlackBuilds.org repository and then let the user browse
through the local mirror and build/install packages from the SlackBuild
scripts contained in the repo.  Sbopkg will fetch the source, check the
md5sum, and the build or build + install a package from the SlackBuild
script.

> If slackbuilds does not support Slamd64, then I am curious what native
> 64-bit distros Slackware developers use... it seems hardware should be
> cheaper nowadays.
>

I imagine Fred Emmott (developer of Slamd64) uses SlackBuilds as well to
recompile the official Slamd64 packages (and perhaps some additional
software he packages for his distro.  However, you would have to ask him
or post in the Slamd64 forums/irc chat for details.  And if you have
specific questions about SlackBuilds.org, you may want to post on their
mailing list or visit #slackbuilds on freenode.

Sbopkg only supports SlackBuilds.org, which in turn only supports
official Slackware.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090202/a1cb8789/attachment.sig>

From dchmelik at hipplanet.com  Mon Feb  2 14:13:13 2009
From: dchmelik at hipplanet.com (dchmelik@gmail.com)
Date: Mon, 2 Feb 2009 06:13:13 -0800 (PST)
Subject: [sbopkg-discuss] Re: source?
In-Reply-To: <20090202034726.GA26756@localhost>
References: <278c9aa8-8d6d-4018-a101-3c01c62e915a@40g2000prx.googlegroups.com>  <20090201191744.2acf416f@liberty.rlwhome.lan> <20090202034726.GA26756@localhost>
Message-ID: <2d5309d0-8a3e-4aa3-88fb-af2e010a384c@t39g2000prh.googlegroups.com>


On Feb 1, 7:47 pm, Chess Griffin <ch... at chessgriffin.com> wrote:
> * Robby Workman <rwork... at slackbuilds.org> [2009-02-01 19:17:44]:
>>>[...]
> > If you open that "binary" up with a text editor, you'll notice that
> > it's actually a script.  There's your source :-)
>
> Yep, like Robby said, sbopkg is simply a shell script.  The tarball
> contains this script, a configuration file, some docs, and two man
> pages.  There is nothing to compile.  In fact, the package I provide
> should work just fine on Slamd64 (notice the 'noarch' in the package
> name).  However, it might be pointless since sbopkg is intended to be
> used with SlackBuilds.org, and SlackBuilds.org does not officially
> support Slamd64.  Still, sbopkg does have the capability to work with a
> custom local non-Slackbuilds.org repository as long as it is set up in a
> similar style to the SlackBuilds.org repo.

I should have realized it was a script (I have seen few that do as
much as compiled programs that are usually larger, and I still think
of .BATs)... it is long for a script; I should learn to code sh like
that.  Some Slamd64 software is recommended to be compiled with
slackbuilds (and maybe a couple modifications;) some are even in the
distro: will sbopkg not compile stuff with it?  The menus usually
work, but often I have seen sbopkg in 'ps ax' output where sbopkg is
usually doing nothing with a dialog program menu showing (which I can
read all of) when it should have already shown in console (though I
have usually done this in KDE konsole with BOINC and lots of stuff
running.)  Maybe I will look closer at the script, though I have less
practice with sh than C....

If slackbuilds does not support Slamd64, then I am curious what native
64-bit distros Slackware developers use... it seems hardware should be
cheaper nowadays.

--David

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Mon Feb  2 03:47:26 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Sun, 1 Feb 2009 22:47:26 -0500
Subject: [sbopkg-discuss] Re: source?
In-Reply-To: <20090201191744.2acf416f@liberty.rlwhome.lan>
References: <278c9aa8-8d6d-4018-a101-3c01c62e915a@40g2000prx.googlegroups.com> <20090201191744.2acf416f@liberty.rlwhome.lan>
Message-ID: <20090202034726.GA26756@localhost>

* Robby Workman <rworkman at slackbuilds.org> [2009-02-01 19:17:44]:

> On Sun, 1 Feb 2009 16:25:54 -0800 (PST)
> "dchmelik at gmail.com" <dchmelik at hipplanet.com> wrote:
> 
> > I have used Slackware since 1997-'8, and I recently downloaded sbopkg
> > 'source,' which seems to just be a binary and docs.  Now I mostly us
> > Slamd64; I would like the source to compile on it: sbopkg often stops
> > for a long time, and I know not if it needs a port or if it just does
> > too much network connecting.
> 
> 
> If you open that "binary" up with a text editor, you'll notice that
> it's actually a script.  There's your source :-)
> 

Yep, like Robby said, sbopkg is simply a shell script.  The tarball
contains this script, a configuration file, some docs, and two man
pages.  There is nothing to compile.  In fact, the package I provide
should work just fine on Slamd64 (notice the 'noarch' in the package
name).  However, it might be pointless since sbopkg is intended to be
used with SlackBuilds.org, and SlackBuilds.org does not officially
support Slamd64.  Still, sbopkg does have the capability to work with a
custom local non-Slackbuilds.org repository as long as it is set up in a
similar style to the SlackBuilds.org repo.

Thanks!


-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090201/9c18a504/attachment.sig>

From rworkman at slackbuilds.org  Mon Feb  2 01:17:44 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 1 Feb 2009 19:17:44 -0600
Subject: [sbopkg-discuss] Re: source?
In-Reply-To: <278c9aa8-8d6d-4018-a101-3c01c62e915a@40g2000prx.googlegroups.com>
References: <278c9aa8-8d6d-4018-a101-3c01c62e915a@40g2000prx.googlegroups.com>
Message-ID: <20090201191744.2acf416f@liberty.rlwhome.lan>

On Sun, 1 Feb 2009 16:25:54 -0800 (PST)
"dchmelik at gmail.com" <dchmelik at hipplanet.com> wrote:

> I have used Slackware since 1997-'8, and I recently downloaded sbopkg
> 'source,' which seems to just be a binary and docs.  Now I mostly us
> Slamd64; I would like the source to compile on it: sbopkg often stops
> for a long time, and I know not if it needs a port or if it just does
> too much network connecting.


If you open that "binary" up with a text editor, you'll notice that
it's actually a script.  There's your source :-)

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090201/35617965/attachment.asc>

From dchmelik at hipplanet.com  Mon Feb  2 00:25:54 2009
From: dchmelik at hipplanet.com (dchmelik@gmail.com)
Date: Sun, 1 Feb 2009 16:25:54 -0800 (PST)
Subject: [sbopkg-discuss] source?
Message-ID: <278c9aa8-8d6d-4018-a101-3c01c62e915a@40g2000prx.googlegroups.com>


I have used Slackware since 1997-'8, and I recently downloaded sbopkg
'source,' which seems to just be a binary and docs.  Now I mostly us
Slamd64; I would like the source to compile on it: sbopkg often stops
for a long time, and I know not if it needs a port or if it just does
too much network connecting.

--David
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From xma at gnu.org  Tue Feb  3 06:38:51 2009
From: xma at gnu.org (xma at gnu.org)
Date: Tue, 03 Feb 2009 07:38:51 +0100
Subject: [sbopkg-discuss] Re: Bzr package
In-Reply-To: <20090202212841.GB16445@localhost>
References: <23903.1233608799@zogzog.maillard.mobi> <20090202212841.GB16445@localhost>
Message-ID: <21565.1233643131@zogzog.maillard.mobi>


Chess Griffin <chess at chessgriffin.com> wrote:

> * xma at gnu.org <xma at gnu.org> [2009-02-02 22:06:39]:
> 
> > To connect to launchpad.net insecurely, use `--no-check-certificate'.
> 
> This is the key.  Add this option to WGETFLAGS in
> /etc/sbopkg/sbopkg.conf and it will work.

It works perfectly. Thank you Chess.

Xavier

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Mon Feb  2 21:28:42 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 2 Feb 2009 16:28:42 -0500
Subject: [sbopkg-discuss] Re: Bzr package
In-Reply-To: <23903.1233608799@zogzog.maillard.mobi>
References: <23903.1233608799@zogzog.maillard.mobi>
Message-ID: <20090202212841.GB16445@localhost>

* xma at gnu.org <xma at gnu.org> [2009-02-02 22:06:39]:

> To connect to launchpad.net insecurely, use `--no-check-certificate'.

This is the key.  Add this option to WGETFLAGS in
/etc/sbopkg/sbopkg.conf and it will work.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090202/4b635a51/attachment.sig>

From xma at gnu.org  Mon Feb  2 21:06:39 2009
From: xma at gnu.org (xma at gnu.org)
Date: Mon, 02 Feb 2009 22:06:39 +0100
Subject: [sbopkg-discuss] Bzr package
Message-ID: <23903.1233608799@zogzog.maillard.mobi>


Hi,

I tried to build bzr with sbopkg -i bzr and it failed:

Building bzr
--2009-02-02 22:04:54--  https://launchpad.net/bzr/1.11/1.11/+download/bzr-1.11.tar.gz
Resolving launchpad.net... 91.189.90.211
Connecting to launchpad.net|91.189.90.211|:443... connected.
ERROR: cannot verify launchpad.net's certificate, issued by `/C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./OU=http://www.starfieldtech.com/repository/CN=Starfield Secure Certification Authority/emailAddress=practices at starfieldtech.com':
  Unable to locally verify the issuer's authority.
To connect to launchpad.net insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.

Would you like to continue processing the rest of the
build queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

Press (Y)es to continue or (N)o to abort.
Y

******************************************
PACKAGE BUILDING/INSTALLATION SUMMARY LOG
Using SlackBuilds.org 12.2 repository

bzr:
Download failed.

******************************************

All done.

This is with latest sbopkg release.

what can I do ?

Regards
-- 
Xavier Maillard

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From phillip.c.warner at gmail.com  Wed Feb 11 17:23:24 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Wed, 11 Feb 2009 11:23:24 -0600
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <20090211123145.GA14464@localhost>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com> <eded84250902101915r6ae86bb0rab29048e62419a62@mail.gmail.com> <20090211032432.GA13906@localhost> <eded84250902110339w12cc0d60k6d8eedb173cafb23@mail.gmail.com> <20090211123145.GA14464@localhost>
Message-ID: <eded84250902110923p780a97a5u3159b7bf515f7a5c@mail.gmail.com>

On Wed, Feb 11, 2009 at 6:31 AM, Chess Griffin <chess at chessgriffin.com>wrote:

>
> I understand -- I guess my point is, if installpkg does not check for
> perms, then should sbopkg since it just calls installpkg (assuming only
> root can install packages in sbopkg)?  And since the default SBo
> behavior is to save the resulting packages in the same world-writable
> directory, /tmp, then again this *might* open the door to other
> modifications like you suggest.  Either way, these problems are not
> specific to sbopkg.  Sbopkg is just a 'front-end' to installpkg, in
> other words.
>
> In any event, if we decide to go forward with the idea of changing
> sbopkg so it sits in /usr/sbin and must be run as root, like slackpkg
> and the various *pkg tools, then presumably this issue is moot because
> the resulting packages from sbopkg would have the root:root perms?


Making sure that sbopkg is only run by root makes no difference for this
issue as sbopkg still would be able to install bad packages not created by
sbopkg.


> Perhaps a warning the package does not have root:root perms would be a
> good idea, regardless.
>
> Yes.  You could also keep a private list of the packages (with file times)
built and ready to be installed and remove them from the list after they
have been moved/deleted.  Another great idea would be to allow the admin to
optionally have more info about the package before installing it.  Output of
'ls -l', a cat of doinst.sh and perhaps the .SlackBuild file, and a total
list of contents would be useful.  If nothing else then the warning and 'ls
-l' output may suffice.  That way the permissions and time of creation could
be seen and the warning would make it obvious it the perms were off.

But what happens if two legitimate SBo packages for the same software are
created?  Right now you are only given the option to install one of them.
You may want to install the other pacakge instead.  If instead you were
shown a 'ls -l' of all the matching packages and then were allowed to choose
which one to install all of this would be more sane.

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090211/e5577c41/attachment.htm>

From chess at chessgriffin.com  Wed Feb 11 12:31:45 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 11 Feb 2009 07:31:45 -0500
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <eded84250902110339w12cc0d60k6d8eedb173cafb23@mail.gmail.com>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com> <eded84250902101915r6ae86bb0rab29048e62419a62@mail.gmail.com> <20090211032432.GA13906@localhost> <eded84250902110339w12cc0d60k6d8eedb173cafb23@mail.gmail.com>
Message-ID: <20090211123145.GA14464@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-02-11 05:39:23]:

> >
> This is not true.  When a root user runs an SBo SlackBuild the created
> package *cannot* be overwritten by a normal user since the package has
> root:root perms with no 'others' write access.  It is true that a user
> could stick a fake package with a similar name in TMP, but the admin
> should be making sure that the package they are installing has the
> correct perms/ownership before installing it, and sbopkg should do the
> same since it automates these build/install steps.
> 

I understand -- I guess my point is, if installpkg does not check for
perms, then should sbopkg since it just calls installpkg (assuming only
root can install packages in sbopkg)?  And since the default SBo
behavior is to save the resulting packages in the same world-writable
directory, /tmp, then again this *might* open the door to other
modifications like you suggest.  Either way, these problems are not
specific to sbopkg.  Sbopkg is just a 'front-end' to installpkg, in
other words.

In any event, if we decide to go forward with the idea of changing
sbopkg so it sits in /usr/sbin and must be run as root, like slackpkg
and the various *pkg tools, then presumably this issue is moot because
the resulting packages from sbopkg would have the root:root perms?
Perhaps a warning the package does not have root:root perms would be a
good idea, regardless.

This is a good discussion, thanks!

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090211/43e508d2/attachment.sig>

From phillip.c.warner at gmail.com  Wed Feb 11 11:39:23 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Wed, 11 Feb 2009 05:39:23 -0600
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <20090211032432.GA13906@localhost>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com> <eded84250902101915r6ae86bb0rab29048e62419a62@mail.gmail.com> <20090211032432.GA13906@localhost>
Message-ID: <eded84250902110339w12cc0d60k6d8eedb173cafb23@mail.gmail.com>


On 2/10/09, Chess Griffin <chess at chessgriffin.com> wrote:
> It would seem to me that the same spoof could happen by a root user
> running an SBo SlackBuild outside, which saves a package to /tmp,
> another user coming along and makes a fake package and overwrites the
> one in /tmp, which root then installs at a later date.
>
> It seems that all of these spoofs involving the SlackBuild, the .info
> file, and the resulting package are inherent in the SBo and SlackBuild
> system, and not sbopkg-specific.
>
This is not true.  When a root user runs an SBo SlackBuild the created
package *cannot* be overwritten by a normal user since the package has
root:root perms with no 'others' write access.  It is true that a user
could stick a fake package with a similar name in TMP, but the admin
should be making sure that the package they are installing has the
correct perms/ownership before installing it, and sbopkg should do the
same since it automates these build/install steps.

Also, before I install packages I run some custom scripts on them to
do various sanity checks on them.  Perhaps you can let sbopkg have the
option to run a post-build script before installing.  The config
option could just point to the script to run and its output would
simply be shown on the console after which sbopkg will regain control
after keyboard input.

If people don't like the root:root sanity check then I again suggest
that you make it possible to turn it off (leave it on by default) by a
simple config switch.  If nothing else, adding a post-build script
option would let me keep this in myself without having to patch every
new sbopkg version.

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Wed Feb 11 03:24:32 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 10 Feb 2009 22:24:32 -0500
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <eded84250902101915r6ae86bb0rab29048e62419a62@mail.gmail.com>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com> <eded84250902101915r6ae86bb0rab29048e62419a62@mail.gmail.com>
Message-ID: <20090211032432.GA13906@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-02-10 21:15:06]:

> 
> On 2/10/09, T2F <bkirkp at gmail.com> wrote:
> >
> > Can someone explain to me why sbopkg insists that the package belong
> > to root:root? I keep my sandbox with the rest of my data on a server
> > partition where the files are owned by bill:data & permissioned 664. I
> > have an hourly cron job that sees to the proper permissions. If I
> > build a package & install it immediately, I have no problems, but if I
> > go back later, for example to install it on my laptop, I have to
> > install from the command line. installpkg has no problems with
> > ownership, why should sbopkg?
> > Regards,
> > Bill
> 
> Not checking for root:root perms opens up a package spoofing
> vunerability in sbopkg.  If this doesn't bother people perhaps the
> check could be allowed to be turned off with a config switch.  Here is
> a portion of the email I previously sent Chess that describes the
> vunerability:
> 
> ===========
> in brief, sbopkg needs to make sure packages in $OUTPUT are owned
> root:root before even offering to install.  If $OUTPUT is world
> writable (such as /tmp) then normal user can make a fake or malicious
> package that makes sbopkg thinks it can install.
> 
> ---- How to spoof SBo packages ----
> simply make sure the package
>   name starts with the PRGNAM (the name can be longer than PRGNAM though)
>   has the corresponding VERSION, BUILDNUM, and TAG
> this info can easily be found in the local or online repo
> 
> Now when the admin views an entry for a SlackBuild they will have the
> option to install this fake package!
> 
> While this may not fool the admin who knows they did not build a
> package, it might be easy to fool an admin by making a fake package
> corresponding to a SBo package that IS in OUTPUT.
> Simply change the ARCH, or if the admin made a custom version or tag,
> then the regular name might work.
> 
> SBo package spoofing could be defeated by making sure:
> 1) that your $OUTPUT is a folder only root has access to
> 2) sbopkg enforces that packages to install have root:root ownership
> ============
> 

Although, after further reflection and discussion with others, I am not
sure this is really an sbopkg issue.  All sbopkg does is run the
SlackBuild and then execute 'installpkg' on what is dropped into /tmp.
It would seem to me that the same spoof could happen by a root user
running an SBo SlackBuild outside, which saves a package to /tmp,
another user coming along and makes a fake package and overwrites the
one in /tmp, which root then installs at a later date.

It seems that all of these spoofs involving the SlackBuild, the .info
file, and the resulting package are inherent in the SBo and SlackBuild
system, and not sbopkg-specific.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090210/93cbcc2e/attachment.sig>

From phillip.c.warner at gmail.com  Wed Feb 11 03:15:06 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Tue, 10 Feb 2009 21:15:06 -0600
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com>
Message-ID: <eded84250902101915r6ae86bb0rab29048e62419a62@mail.gmail.com>


On 2/10/09, T2F <bkirkp at gmail.com> wrote:
>
> Can someone explain to me why sbopkg insists that the package belong
> to root:root? I keep my sandbox with the rest of my data on a server
> partition where the files are owned by bill:data & permissioned 664. I
> have an hourly cron job that sees to the proper permissions. If I
> build a package & install it immediately, I have no problems, but if I
> go back later, for example to install it on my laptop, I have to
> install from the command line. installpkg has no problems with
> ownership, why should sbopkg?
> Regards,
> Bill

Not checking for root:root perms opens up a package spoofing
vunerability in sbopkg.  If this doesn't bother people perhaps the
check could be allowed to be turned off with a config switch.  Here is
a portion of the email I previously sent Chess that describes the
vunerability:

===========
in brief, sbopkg needs to make sure packages in $OUTPUT are owned
root:root before even offering to install.  If $OUTPUT is world
writable (such as /tmp) then normal user can make a fake or malicious
package that makes sbopkg thinks it can install.

---- How to spoof SBo packages ----
simply make sure the package
  name starts with the PRGNAM (the name can be longer than PRGNAM though)
  has the corresponding VERSION, BUILDNUM, and TAG
this info can easily be found in the local or online repo

Now when the admin views an entry for a SlackBuild they will have the
option to install this fake package!

While this may not fool the admin who knows they did not build a
package, it might be easy to fool an admin by making a fake package
corresponding to a SBo package that IS in OUTPUT.
Simply change the ARCH, or if the admin made a custom version or tag,
then the regular name might work.

SBo package spoofing could be defeated by making sure:
1) that your $OUTPUT is a folder only root has access to
2) sbopkg enforces that packages to install have root:root ownership
============

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From bkirkp at gmail.com  Wed Feb 11 01:41:07 2009
From: bkirkp at gmail.com (T2F)
Date: Tue, 10 Feb 2009 17:41:07 -0800 (PST)
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <20090211004520.GB13676@localhost>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com>  <20090211004520.GB13676@localhost>
Message-ID: <de90316a-7baa-4f4f-a590-48e1234fd26f@g39g2000pri.googlegroups.com>




On Feb 10, 6:45?pm, Chess Griffin <ch... at chessgriffin.com> wrote:
> * T2F <bki... at gmail.com> [2009-02-10 15:39:47]:
>
>
>
> > Can someone explain to me why sbopkg insists that the package belong
> > to root:root? I keep my sandbox with the rest of my data on a server
> > partition where the files are owned by bill:data & permissioned 664. I
> > have an hourly cron job that sees to the proper permissions. If I
> > build a package & install it immediately, I have no problems, but if I
> > go back later, for example to install it on my laptop, I have to
> > install from the command line. installpkg has no problems with
> > ownership, why should sbopkg?
> > Regards,
> > Bill
>
> Well, this was added to prevent a potential security risk since sbopkg
> had the capability of being run as a root or non-root user. ?Howevever,
> this restriction may be eliminated as we are currently discussing
> removing the ability to run sbopkg as a non-root user and require it to
> be run as root only, just like pkgtool, slackpkg, etc. ?In fact, I was
> going to post something here to the ML asking whether anyone really
> needed the ability to use sbopkg as a non-root user. ?The current
> 'user-mode' in sbopkg is deficient in many ways, and causes problems
> such as this one you raise.
>
> In my opinion, I think sbopkg should be just like those other tools and
> require root permissions to run. ?If that was the case, then I do not
> believe it would need to check for ownership or permissions of packages.
>
> In the meantime, if you want to comment out lines 1572-1576 in
> /usr/bin/sbopkg that will skip this check.
>
> --
> Chess Griffin
>
Hi, Chess,
Yep, I had found those lines, but haven't yet commented them out. Will
do so. I think requiring "root" to run is a good idea.
Regards,
Bill

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Wed Feb 11 00:45:20 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 10 Feb 2009 19:45:20 -0500
Subject: [sbopkg-discuss] Re: Package ownership
In-Reply-To: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com>
References: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com>
Message-ID: <20090211004520.GB13676@localhost>

* T2F <bkirkp at gmail.com> [2009-02-10 15:39:47]:

> 
> Can someone explain to me why sbopkg insists that the package belong
> to root:root? I keep my sandbox with the rest of my data on a server
> partition where the files are owned by bill:data & permissioned 664. I
> have an hourly cron job that sees to the proper permissions. If I
> build a package & install it immediately, I have no problems, but if I
> go back later, for example to install it on my laptop, I have to
> install from the command line. installpkg has no problems with
> ownership, why should sbopkg?
> Regards,
> Bill

Well, this was added to prevent a potential security risk since sbopkg
had the capability of being run as a root or non-root user.  Howevever,
this restriction may be eliminated as we are currently discussing
removing the ability to run sbopkg as a non-root user and require it to
be run as root only, just like pkgtool, slackpkg, etc.  In fact, I was
going to post something here to the ML asking whether anyone really
needed the ability to use sbopkg as a non-root user.  The current
'user-mode' in sbopkg is deficient in many ways, and causes problems
such as this one you raise.

In my opinion, I think sbopkg should be just like those other tools and
require root permissions to run.  If that was the case, then I do not
believe it would need to check for ownership or permissions of packages.

In the meantime, if you want to comment out lines 1572-1576 in
/usr/bin/sbopkg that will skip this check.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090210/44161a76/attachment.sig>

From bkirkp at gmail.com  Tue Feb 10 23:39:47 2009
From: bkirkp at gmail.com (T2F)
Date: Tue, 10 Feb 2009 15:39:47 -0800 (PST)
Subject: [sbopkg-discuss] Package ownership
Message-ID: <968e2ee5-e5cb-4a62-a331-798b61d27124@t26g2000prh.googlegroups.com>


Can someone explain to me why sbopkg insists that the package belong
to root:root? I keep my sandbox with the rest of my data on a server
partition where the files are owned by bill:data & permissioned 664. I
have an hourly cron job that sees to the proper permissions. If I
build a package & install it immediately, I have no problems, but if I
go back later, for example to install it on my laptop, I have to
install from the command line. installpkg has no problems with
ownership, why should sbopkg?
Regards,
Bill
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From mauro.giachero at gmail.com  Wed Feb 11 09:38:42 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 11 Feb 2009 10:38:42 +0100
Subject: [sbopkg-discuss] Re: Moving sbopkg to /usr/sbin and require root
In-Reply-To: <20090211011300.GA13725@localhost>
References: <20090211011300.GA13725@localhost>
Message-ID: <da3e877f0902110138n55b6c29eme3d49f8232df1bde@mail.gmail.com>

I also think that user-mode support should be tossed.

-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090211/c5f94dd7/attachment.htm>

From joao.eel at gmail.com  Wed Feb 11 02:32:12 2009
From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=)
Date: Wed, 11 Feb 2009 00:32:12 -0200
Subject: [sbopkg-discuss] Re: [Slackbuilds-users] Moving sbopkg to /usr/sbin
 and require root
In-Reply-To: <5eb6ff2c0902101755i352d1862t3fd25dcbf3e75481@mail.gmail.com>
References: <20090211011300.GA13725@localhost> <a6f13f000902101726j4a2e1c08hd61ca83ff6562762@mail.gmail.com> <5eb6ff2c0902101755i352d1862t3fd25dcbf3e75481@mail.gmail.com>
Message-ID: <ecb28420902101832j535aef9bm46e27acbee6ed3eb@mail.gmail.com>


Only root is good. When I want to test a SlackBuild before building it
as root, i just use the one at the "rsynced" tree to do it by hand.

-- Jo?o

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Wed Feb 11 01:13:01 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 10 Feb 2009 20:13:01 -0500
Subject: [sbopkg-discuss] Moving sbopkg to /usr/sbin and require root
Message-ID: <20090211011300.GA13725@localhost>

Sorry for the cross-post to sbopkg and slackbuilds.org mailing lists but
I want to get as much feedback as possible.

Currently, sbopkg can be run by root or a non-root user.  Certain
functions or features can only be done by a root user, of course, like
building and installing packages.  However, trying to maintain this dual
permission standard is becoming very problematic.  More than once I have
considered removing the 'user-mode' from sbopkg, move sbopkg to
/usr/sbin, and require sbopkg be run only by the root user, like
pkgtool, slackpkg, and other similar tools require.  Several unrelated
issues have brought this to the forefront again and I am now very much
leaning towards making this change.

So, the question is:  how many people feel strongly about keeping the
ability to run sbopkg as a non-root user?  Could folks adapt to using
sbopkg only as root?

Feel free to respond on the list or privately.

Thank you in advance for your feedback.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090210/ca7ff437/attachment.sig>

From phillip.c.warner at gmail.com  Wed Feb 18 04:46:11 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Tue, 17 Feb 2009 22:46:11 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com> <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com> <da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com> <da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>
Message-ID: <eded84250902172046y5df2a6b1ue24d7247010d8eeb@mail.gmail.com>


On 2/17/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> This other patch, based once again on a suggestion from slakmagik, should be
> even better. Applies on r457, not on top of the previous one (which you can
> safely discard, I suppose).
This patch works great here.  However, I do also have the problem with
screen*, so if you could add that to the list of TERMs using the
workaround please.  That should do it.

Changing TERM=xterm does fix the problem as well, but I don't think
that it is a good idea for root to lie about what terminal
capabilities the terminal actually has.  Also, in a screen session
this causes graphical errors (though at least you can see the dialog
boxes).

thank you,
--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Tue Feb 17 23:29:28 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 17 Feb 2009 18:29:28 -0500
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902170247v47a2a6e9jb5b82de23f589106@mail.gmail.com>
References: <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com> <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com> <da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com> <da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com> <da3e877f0902170247v47a2a6e9jb5b82de23f589106@mail.gmail.com>
Message-ID: <20090217232928.GD4322@localhost>

* Mauro Giachero <mauro.giachero at gmail.com> [2009-02-17 11:47:18]:

> Sorry for spamming the list...
> What if you simply start sbopkg with
>     TERM=xterm sbopkg
> ? Here in aterm seems to work...
> 

The more I think about this issue, the more I think it's not really an
sbopkg problem.  I believe the fix (if any) should be as minimal as
possible.  Including a wrapper script really might be all that's needed.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/d6ef484f/attachment.sig>

From mauro.giachero at gmail.com  Tue Feb 17 10:47:18 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Tue, 17 Feb 2009 11:47:18 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com> <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com> <da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com> <da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>
Message-ID: <da3e877f0902170247v47a2a6e9jb5b82de23f589106@mail.gmail.com>

Sorry for spamming the list...
What if you simply start sbopkg with
    TERM=xterm sbopkg
? Here in aterm seems to work...

-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/c06f2ff7/attachment.htm>

From mauro.giachero at gmail.com  Tue Feb 17 10:38:21 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Tue, 17 Feb 2009 11:38:21 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com> <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com> <da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com>
Message-ID: <da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>

This other patch, based once again on a suggestion from slakmagik, should be
even better. Applies on r457, not on top of the previous one (which you can
safely discard, I suppose).

-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/f4720f1d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Make-the-rxvt-workaround-easier-on-the-CPU-and-matc-2.patch
Type: text/x-diff
Size: 1493 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/f4720f1d/attachment.bin>

From mauro.giachero at gmail.com  Tue Feb 17 09:41:51 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Tue, 17 Feb 2009 10:41:51 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com> <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>
Message-ID: <da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com>

Hello Phillip,

On Tue, Feb 17, 2009 at 1:53 AM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:

>
> The code does not work well for me.  Instead it actually creates a
> memory sink hole and the excessive grepping hogs the CPU (bogging down
> my poor PII).


Do you mean that what is in SVN is worse than the wrapper?


> I recommend taking it out of SVN.


Will do, if we don't get to a better solution.


> Perhaps instead a trap can be used to manually call a refresh.  The
> user presses CTRL+l (lower 'L) and the screen refreshes then.


I'd prefer to work a while on something not trashing the program usability
before...


> As an alternative, a wrapper could be written for all of the dialog
> commands.  That way the code can still be clean, but the wrapper will
> manually cause a refresh.


Let's try some alternatives before such an invasive change.
Does the situation improve if you apply the attached patch?

On Mon, Feb 16, 2009 at 9:40 PM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:
>
> I have not gotten a chance to try this out yet, but after looking at the
> patch I'd suggest a minor change.  Right now the function is only called if
> Term="rxvt", but what about rxvt-unicode or screen?


I can match "^rxvt.*", for sure.
Have you had any problem on $TERM==screen? We don't want the workaround
enabled on good configurations.


> Instead of checking for TERM, I suggest that you simply have a switch to
> activate the function.  That way the admin can decide on the fly without
> having to modify the script itself.


I don't agree here, at least not as our first attempt (maybe as a fallback).
I'd prefer sbopkg to work right out of the box without requiring the admin
to enable strange workarounds.


> --phillip
>

Thank you for your feedback
-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/0144a701/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Make-the-rxvt-workaround-easier-on-the-CPU-and-matc.patch
Type: text/x-diff
Size: 1446 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090217/0144a701/attachment.bin>

From chess at chessgriffin.com  Tue Feb 17 02:38:39 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 16 Feb 2009 21:38:39 -0500 (EST)
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com> <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>
Message-ID: <57806.68.115.233.50.1234838319.squirrel@webmail.tuffmail.net>


> The code does not work well for me.  Instead it actually creates a
> memory sink hole and the excessive grepping hogs the CPU (bogging down
> my poor PII).  I recommend taking it out of SVN.
>
> Perhaps instead a trap can be used to manually call a refresh.  The
> user presses CTRL+l (lower 'L) and the screen refreshes then.
>
> As an alternative, a wrapper could be written for all of the dialog
> commands.  That way the code can still be clean, but the wrapper will
> manually cause a refresh.
>
> --phillip
>

Phillip, thanks for your posts.  I am currently traveling and will be out
of pocket for a solid day but should be back around on Wed.  In the
meantime, I am sure Mauro will respond to this issue.  Perhaps turning it
back into a simple wrapper is the way to go.

Thanks again for all the testing and feedback, it is greatly appreciated.

-- 
Chess Griffin


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From phillip.c.warner at gmail.com  Tue Feb 17 00:53:31 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 18:53:31 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com> <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com>
Message-ID: <eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>


The code does not work well for me.  Instead it actually creates a
memory sink hole and the excessive grepping hogs the CPU (bogging down
my poor PII).  I recommend taking it out of SVN.

Perhaps instead a trap can be used to manually call a refresh.  The
user presses CTRL+l (lower 'L) and the screen refreshes then.

As an alternative, a wrapper could be written for all of the dialog
commands.  That way the code can still be clean, but the wrapper will
manually cause a refresh.

--phillip

On 2/16/09, Phillip Warner <phillip.c.warner at gmail.com> wrote:
> On Mon, Feb 16, 2009 at 11:41 AM, Mauro Giachero
> <mauro.giachero at gmail.com>wrote:
>
>> I just committed a similar workaround to SVN (revision 457). If
>> everything
>> works as expected, the wrapper should no longer be required.
>>
>> Please let us know if this fixes the problem for you, and feel free to
>> raise the issue again if it doesn't.
>>
>> I have not gotten a chance to try this out yet, but after looking at the
> patch I'd suggest a minor change.  Right now the function is only called if
> Term="rxvt", but what about rxvt-unicode or screen?  Instead of checking
> for
> TERM, I suggest that you simply have a switch to activate the function.
> That way the admin can decide on the fly without having to modify the
> script
> itself.
>
> I'm going to try out sspm and start testing svn sometime this week.  I'll
> report back on this and the diff stuff after I am done testing.
>
> --phillip
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From phillip.c.warner at gmail.com  Mon Feb 16 20:40:35 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 14:40:35 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com> <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com>
Message-ID: <eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com>

On Mon, Feb 16, 2009 at 11:41 AM, Mauro Giachero
<mauro.giachero at gmail.com>wrote:

> I just committed a similar workaround to SVN (revision 457). If everything
> works as expected, the wrapper should no longer be required.
>
> Please let us know if this fixes the problem for you, and feel free to
> raise the issue again if it doesn't.
>
> I have not gotten a chance to try this out yet, but after looking at the
patch I'd suggest a minor change.  Right now the function is only called if
Term="rxvt", but what about rxvt-unicode or screen?  Instead of checking for
TERM, I suggest that you simply have a switch to activate the function.
That way the admin can decide on the fly without having to modify the script
itself.

I'm going to try out sspm and start testing svn sometime this week.  I'll
report back on this and the diff stuff after I am done testing.

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/584329a6/attachment.htm>

From mauro.giachero at gmail.com  Mon Feb 16 17:41:57 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Mon, 16 Feb 2009 18:41:57 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com> <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com>
Message-ID: <da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com>

I just committed a similar workaround to SVN (revision 457). If everything
works as expected, the wrapper should no longer be required.

Please let us know if this fixes the problem for you, and feel free to raise
the issue again if it doesn't.

Thank you again for the report.
-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/4d9ba768/attachment.htm>

From phillip.c.warner at gmail.com  Mon Feb 16 16:45:30 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 10:45:30 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com> <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com>
Message-ID: <eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com>


I can see why.  Thank you again.

On 2/16/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> Actually, this one is far less buggy.
> --
> Mauro Giachero
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From mauro.giachero at gmail.com  Mon Feb 16 16:07:12 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Mon, 16 Feb 2009 17:07:12 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com> <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com>
Message-ID: <da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com>

Actually, this one is far less buggy.
-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/04fb6c37/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbopkg-rxvt
Type: application/octet-stream
Size: 295 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/04fb6c37/attachment.obj>

From phillip.c.warner at gmail.com  Mon Feb 16 14:39:46 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 08:39:46 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com> <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com>
Message-ID: <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com>


Agreed.  It would add too much clutter.  The short script should work fine.

Thank you.

--phillip

On 2/16/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> On Mon, Feb 16, 2009 at 9:17 AM, Phillip Warner
> <phillip.c.warner at gmail.com>wrote:
>
>>
>> On 2/11/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
>> > After a bit of googling I found [1], and I verified that sending a
>> SIGWINCH
>> > to the dialog process makes the dialog appear.
>> > I'm not sure whether working around it on the sbopkg side is feasible,
>> > though.
>> I just tested this and I think that this could be done in sbopkg if
>> the 'dialog --clear' statements do not work.
>>
>> For example, something like this may work.
>>  exec dialog_process &
>>  dpid=$!
>>  .
>>  .
>>  .
>>  kill -SIGWINCH $dpid
>>
>> --phillip
>>
>
> Of course, but that would clutter the code really too much!
> What if, instead, you use the attached script to start sbopkg? Quickly
> tested here in aterm, and seems to work.
> (I agree that's dirty and suboptimal, but makes sbopkg usable in aterm and I
> don't see huge downsides...)
>
> --
> Mauro Giachero
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From mauro.giachero at gmail.com  Mon Feb 16 10:10:37 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Mon, 16 Feb 2009 11:10:37 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com> <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com>
Message-ID: <da3e877f0902160210sce9b3d9x55d77700f0aa2680@mail.gmail.com>

On Mon, Feb 16, 2009 at 9:17 AM, Phillip Warner
<phillip.c.warner at gmail.com>wrote:

>
> On 2/11/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> > After a bit of googling I found [1], and I verified that sending a
> SIGWINCH
> > to the dialog process makes the dialog appear.
> > I'm not sure whether working around it on the sbopkg side is feasible,
> > though.
> I just tested this and I think that this could be done in sbopkg if
> the 'dialog --clear' statements do not work.
>
> For example, something like this may work.
>  exec dialog_process &
>  dpid=$!
>  .
>  .
>  .
>  kill -SIGWINCH $dpid
>
> --phillip
>

Of course, but that would clutter the code really too much!
What if, instead, you use the attached script to start sbopkg? Quickly
tested here in aterm, and seems to work.
(I agree that's dirty and suboptimal, but makes sbopkg usable in aterm and I
don't see huge downsides...)

-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/546b57c5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbopkg-rxvt
Type: application/octet-stream
Size: 185 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090216/546b57c5/attachment.obj>

From phillip.c.warner at gmail.com  Mon Feb 16 08:17:09 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Mon, 16 Feb 2009 02:17:09 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com>
Message-ID: <eded84250902160017gbdcb88apa9c8fc215b3fe477@mail.gmail.com>


On 2/11/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> After a bit of googling I found [1], and I verified that sending a SIGWINCH
> to the dialog process makes the dialog appear.
> I'm not sure whether working around it on the sbopkg side is feasible,
> though.
I just tested this and I think that this could be done in sbopkg if
the 'dialog --clear' statements do not work.

For example, something like this may work.
  exec dialog_process &
  dpid=$!
  .
  .
  .
  kill -SIGWINCH $dpid

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From phillip.c.warner at gmail.com  Wed Feb 11 19:44:34 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Wed, 11 Feb 2009 13:44:34 -0600
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <20090211141954.GA11399@localhost>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com> <20090211141954.GA11399@localhost>
Message-ID: <eded84250902111144i36201fceu4b66760be28adea1@mail.gmail.com>

On Wed, Feb 11, 2009 at 8:19 AM, Chess Griffin <chess at chessgriffin.com>wrote:

>
> I *think* this can be fixed by adding some 'dialog --clear' commands
> throughout sbopkg at each new menu screen.  I will test this out and see
> if it helps.
>
> Could you send me a patch when you are done so I can test it on my machine
as well?

thank you,

--phillip

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090211/050fae00/attachment.htm>

From mauro.giachero at gmail.com  Wed Feb 11 14:46:03 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 11 Feb 2009 15:46:03 +0100
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com>
Message-ID: <da3e877f0902110646t34983ad9w462a35066fe36b7b@mail.gmail.com>

I can reproduce it in aterm, but also with pkgtool... So looks like an
rxvt-ncurses problem.
After a bit of googling I found [1], and I verified that sending a SIGWINCH
to the dialog process makes the dialog appear.
I'm not sure whether working around it on the sbopkg side is feasible,
though.

[1] http://lists.debian.org/debian-user/2008/06/msg00116.html

-- 
Mauro Giachero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090211/a71238ba/attachment.htm>

From chess at chessgriffin.com  Wed Feb 11 14:19:55 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 11 Feb 2009 09:19:55 -0500
Subject: [sbopkg-discuss] Re: Terminals needing refreshing to see sbopkg
In-Reply-To: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com>
Message-ID: <20090211141954.GA11399@localhost>

* shadowsnipes <phillip.c.warner at gmail.com> [2009-02-11 04:52:39]:

> 
> On some terminal emulators I have to resize the window at each new
> sbopkg menu in order to see the 'GUI'.  This is not a problem with
> pkgtool, however, which uses dialog as well.
> 
> The problematic terminals are (all created from SBo):
>   aterm
>   urxvt
>   mrxvt
> 
> These work fine, however (and are all a part of stock SW packages) .
>   xterm
>   rxvt
>   Terminal
> 
> has anyone else had similar problems and know the solution?  Perhaps
> slight adjustments can be made to the sbopkg code so that it works in
> these terminals as well (as dialog in pkgtool does).
> 

I *think* this can be fixed by adding some 'dialog --clear' commands
throughout sbopkg at each new menu screen.  I will test this out and see
if it helps.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090211/27de1f9f/attachment.sig>

From phillip.c.warner at gmail.com  Wed Feb 11 12:52:39 2009
From: phillip.c.warner at gmail.com (shadowsnipes)
Date: Wed, 11 Feb 2009 04:52:39 -0800 (PST)
Subject: [sbopkg-discuss] Terminals needing refreshing to see sbopkg
Message-ID: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com>


On some terminal emulators I have to resize the window at each new
sbopkg menu in order to see the 'GUI'.  This is not a problem with
pkgtool, however, which uses dialog as well.

The problematic terminals are (all created from SBo):
  aterm
  urxvt
  mrxvt

These work fine, however (and are all a part of stock SW packages) .
  xterm
  rxvt
  Terminal

has anyone else had similar problems and know the solution?  Perhaps
slight adjustments can be made to the sbopkg code so that it works in
these terminals as well (as dialog in pkgtool does).

--phillip
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess at chessgriffin.com  Wed Feb 18 15:09:00 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 18 Feb 2009 10:09:00 -0500
Subject: [sbopkg-discuss] [jsunx1@bellsouth.net: sbopkg-discuss issues]
Message-ID: <20090218150859.GA9130@localhost>

Slakmagik was having troubles posting to this list and so I wanted to
pass his comments on.  His comments relate to the DIFF stuff and the
TERM issues.

-- 
Chess Griffin
-------------- next part --------------
An embedded message was scrubbed...
From: slakmagik <jsunx1 at bellsouth.net>
Subject: sbopkg-discuss issues
Date: Mon, 16 Feb 2009 20:20:14 -0500
Size: 8230
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090218/0f7a6387/attachment.eml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090218/0f7a6387/attachment.sig>

From xma at gnu.org  Wed Feb 18 21:25:03 2009
From: xma at gnu.org (Xavier Maillard)
Date: Wed, 18 Feb 2009 22:25:03 +0100
Subject: No subject
Message-ID: <200902182125.n1ILP3UN002782@zogzog.maillard.mobi>


Hi,

I am not really interested in seing sbopkg-devel discussions
(though I really like sbopkg tool), I would like to know whether
new releases are announced on another list or do you announce it
also on SBo lists as well ?

If so, I could unsubscribe this list.

Best regards,
	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group.
To post to this group, send email to sbopkg-discuss at googlegroups.com
To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---



From chess.griffin at gmail.com  Wed Feb 18 22:43:25 2009
From: chess.griffin at gmail.com (Chess Griffin)
Date: Wed, 18 Feb 2009 17:43:25 -0500
Subject: sbopkg devel discussions
In-Reply-To: <200902182125.n1ILP3UN002782@zogzog.maillard.mobi>
References: <200902182125.n1ILP3UN002782@zogzog.maillard.mobi>
Message-ID: <20090218224324.GA3093@localhost>

* Xavier Maillard <xma at gnu.org> [2009-02-18 22:25:03]:

> 
> Hi,
> 
> I am not really interested in seing sbopkg-devel discussions
> (though I really like sbopkg tool), I would like to know whether
> new releases are announced on another list or do you announce it
> also on SBo lists as well ?
> 
> If so, I could unsubscribe this list.
> 
> Best regards,
> 	Xavier

I announce all new releases on this list and the SBo list.  I am
actually in the process of moving the sbopkg mailing list to a standard
mailman setup.  Maybe there can be a second 'announcement' only list or
something if there is enough of a need for separate lists.

-- 
Chess Griffin


From phillip.c.warner at gmail.com  Thu Feb 19 19:39:13 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Thu, 19 Feb 2009 13:39:13 -0600
Subject: [sbopkg-users] [sbopkg-discuss] Re: Terminals needing
	refreshing to see sbopkg
In-Reply-To: <eded84250902172046y5df2a6b1ue24d7247010d8eeb@mail.gmail.com>
References: <e98ecbf4-5172-461a-aa9e-4b8c02526741@v13g2000yqm.googlegroups.com>
	<eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com>
	<da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com>
	<eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com>
	<da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com>
	<eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com>
	<eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>
	<da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com>
	<da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>
	<eded84250902172046y5df2a6b1ue24d7247010d8eeb@mail.gmail.com>
Message-ID: <eded84250902191139w108191e6g92720514ca819bc1@mail.gmail.com>

The newest fix in r458+ works well.  It makes sbopkg a lot more usable now
in my virtual terminals.  Thank you.

--phillip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090219/6c4e2a05/attachment.html>

From chess at chessgriffin.com  Thu Feb 19 21:53:15 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 19 Feb 2009 16:53:15 -0500
Subject: [sbopkg-users] [sbopkg-discuss] Re: Terminals
	needing	refreshing to see sbopkg
In-Reply-To: <eded84250902191139w108191e6g92720514ca819bc1@mail.gmail.com>
References: <eded84250902160639n5ff6ec2bvf7e1572f9f998e8c@mail.gmail.com>
	<da3e877f0902160807i17074c00sf150aaddbed3452f@mail.gmail.com>
	<eded84250902160845i1762973bx8e9309456c71a370@mail.gmail.com>
	<da3e877f0902160941r66ef4311se39606b79fa47783@mail.gmail.com>
	<eded84250902161240qa51c0b9g645307c07c18f883@mail.gmail.com>
	<eded84250902161653r6ef071b2vc06e44db94c7e8f6@mail.gmail.com>
	<da3e877f0902170141k47327a74ke92c7329578745e7@mail.gmail.com>
	<da3e877f0902170238x6b622dc9t8c9446d1833c9324@mail.gmail.com>
	<eded84250902172046y5df2a6b1ue24d7247010d8eeb@mail.gmail.com>
	<eded84250902191139w108191e6g92720514ca819bc1@mail.gmail.com>
Message-ID: <20090219215315.GA7300@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-02-19 13:39:13]:

> The newest fix in r458+ works well.  It makes sbopkg a lot more usable now
> in my virtual terminals.  Thank you.
> 
> --phillip

Great!  I am glad it is working well.  Please don't hesitate to post or
email if you spot any other issues or areas that need improvement.
Thanks very much for your suggestions and contributions, Phillip.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090219/17478f2a/attachment.sig>

From me at alkos333.net  Thu Feb 19 22:26:39 2009
From: me at alkos333.net (alkos333)
Date: Thu, 19 Feb 2009 16:26:39 -0600
Subject: [sbopkg-users] Testing New List
Message-ID: <a6f13f000902191426yd587c2ek5942ba73ac59bf6f@mail.gmail.com>

Just thought I'd post something to the new list and see if anything
echos back :P

-- 

George Burns  - "I would go out with women my age, but there are no
women my age."

From chess at chessgriffin.com  Thu Feb 19 22:34:53 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 19 Feb 2009 17:34:53 -0500
Subject: [sbopkg-users] Testing New List
In-Reply-To: <a6f13f000902191426yd587c2ek5942ba73ac59bf6f@mail.gmail.com>
References: <a6f13f000902191426yd587c2ek5942ba73ac59bf6f@mail.gmail.com>
Message-ID: <20090219223453.GA7331@localhost>

* alkos333 <me at alkos333.net> [2009-02-19 16:26:39]:

> Just thought I'd post something to the new list and see if anything
> echos back :P
> 

ECHOS BACK ... ECHOS back ... echos back

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090219/a3db80ea/attachment.sig>

From me at alkos333.net  Thu Feb 19 22:37:10 2009
From: me at alkos333.net (alkos333)
Date: Thu, 19 Feb 2009 16:37:10 -0600
Subject: [sbopkg-users] Testing New List
In-Reply-To: <20090219223453.GA7331@localhost>
References: <a6f13f000902191426yd587c2ek5942ba73ac59bf6f@mail.gmail.com>
	<20090219223453.GA7331@localhost>
Message-ID: <a6f13f000902191437s5c500f41n317aef49b7b3b809@mail.gmail.com>

On Thu, Feb 19, 2009 at 4:34 PM, Chess Griffin <chess at chessgriffin.com> wrote:
> * alkos333 <me at alkos333.net> [2009-02-19 16:26:39]:
>
>> Just thought I'd post something to the new list and see if anything
>> echos back :P
>>
>
> ECHOS BACK ... ECHOS back ... echos back
>
> --
> Chess Griffin
>
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>
>

This is awesome :).... awesome ... awesome....

-- 

Bill Watterson  - "There is not enough time to do all the nothing we
want to do."

From jsunx1 at bellsouth.net  Thu Feb 19 22:51:07 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Thu, 19 Feb 2009 17:51:07 -0500
Subject: [sbopkg-users] Testing New List
In-Reply-To: <a6f13f000902191437s5c500f41n317aef49b7b3b809@mail.gmail.com>
References: <a6f13f000902191426yd587c2ek5942ba73ac59bf6f@mail.gmail.com>
	<20090219223453.GA7331@localhost>
	<a6f13f000902191437s5c500f41n317aef49b7b3b809@mail.gmail.com>
Message-ID: <20090219225107.GA8655@surfandslam>

On 2009-02-19 (Thu) 16:37:10 [-0600], alkos333 wrote:
> On Thu, Feb 19, 2009 at 4:34 PM, Chess Griffin <chess at chessgriffin.com> wrote:
> > * alkos333 <me at alkos333.net> [2009-02-19 16:26:39]:
> >
> >> Just thought I'd post something to the new list and see if anything
> >> echos back :P
> >>
> >
> > ECHOS BACK ... ECHOS back ... echos back
> >
> 
> This is awesome :).... awesome ... awesome....
> 

I'm going to try as well, just to make sure I don't get disappointed
when I really want to post something, and to make sure mutt and procmail
are happy. Of course, if everybody were to do this, it might end up
being a long thread.

Hello sbopkg-users world.

From me at alkos333.net  Thu Feb 19 23:16:24 2009
From: me at alkos333.net (alkos333)
Date: Thu, 19 Feb 2009 17:16:24 -0600
Subject: [sbopkg-users] Testing New List
In-Reply-To: <20090219225107.GA8655@surfandslam>
References: <a6f13f000902191426yd587c2ek5942ba73ac59bf6f@mail.gmail.com>
	<20090219223453.GA7331@localhost>
	<a6f13f000902191437s5c500f41n317aef49b7b3b809@mail.gmail.com>
	<20090219225107.GA8655@surfandslam>
Message-ID: <a6f13f000902191516u4c36660fr2870e5de761b2e3c@mail.gmail.com>

On Thu, Feb 19, 2009 at 4:51 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
> On 2009-02-19 (Thu) 16:37:10 [-0600], alkos333 wrote:
>> On Thu, Feb 19, 2009 at 4:34 PM, Chess Griffin <chess at chessgriffin.com> wrote:
>> > * alkos333 <me at alkos333.net> [2009-02-19 16:26:39]:
>> >
>> >> Just thought I'd post something to the new list and see if anything
>> >> echos back :P
>> >>
>> >
>> > ECHOS BACK ... ECHOS back ... echos back
>> >
>>
>> This is awesome :).... awesome ... awesome....
>>
>
> I'm going to try as well, just to make sure I don't get disappointed
> when I really want to post something, and to make sure mutt and procmail
> are happy. Of course, if everybody were to do this, it might end up
> being a long thread.
>
> Hello sbopkg-users world.
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>

This is a nice world, isn't it :)

-- 

George Burns  - "I would go out with women my age, but there are no
women my age."

From phillip.c.warner at gmail.com  Fri Feb 20 02:42:40 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Thu, 19 Feb 2009 20:42:40 -0600
Subject: [sbopkg-users] Install package error checking, options
Message-ID: <eded84250902191842r5856888fqc630ad528c8008f0@mail.gmail.com>

It is good that the option to install packages now checks the
permisions and warns the user if they are not root:root.  However,
there is still the problem that sbopkg makes bad assumptions on what
package to install.

Let's say that you have to SBo packages in /tmp.  One is i486 and the
other is i686 (there can be other differences- the important thing is
that they are SBo packages for the same software).  You may want to
install the i686 version, but you are only given the option to install
the i486 version.

--- Solution - let the user pick from a list  ---
What should happen is that the menu should only display that one
package if it is the only one.  Otherwise, it should display something
like "choose...", and when you select "install" it should pop up a
list of all the matching packages with their corresponding 'ls -l'
output.  The default package selected would ideally be the one that
matches the build info from the last build for that software.

Once the desired package is selected the install process should
proceed as normal (including popping up a warning if root:root perms
are not present).

--- Minor cleanup on error checking needed ---
An interesting thing happens if the default package to be installed is
removed before "install" is selected.  You will get a couple of stat
errors and then the program complains that the package does not have
root:root perms (really it has none :)  ).  Then, when it tries to 'ls
-l' the package there is of course more nasty errors.  If you choose
to install it, it will obviously fail and no harm seems to be done.

--phillip

From phillip.c.warner at gmail.com  Fri Feb 20 03:27:09 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Thu, 19 Feb 2009 21:27:09 -0600
Subject: [sbopkg-users] [sbopkg-discuss] Re: Feature request - show diffs
In-Reply-To: <20090218142057.GA4461@localhost>
References: <eeeead10-3c2f-4f23-a75a-5adc6f5b19cf@d32g2000yqe.googlegroups.com>
	<eded84250902160705h4f71e6e2o55fb46629fc9fe47@mail.gmail.com>
	<da3e877f0902160721p184e93ebsd110014600a657c3@mail.gmail.com>
	<eded84250902161518y3e31c619x458b1e55ded4ee4b@mail.gmail.com>
	<eded84250902161612q188c44eagfdc9f8fc80187b2d@mail.gmail.com>
	<da3e877f0902170202y227652e2w34e14d6c237d6852@mail.gmail.com>
	<20090217232346.GC4322@localhost>
	<eded84250902172129t3f2480a0n2f51a76189d0a629@mail.gmail.com>
	<da3e877f0902180103t667587c5n55a73df088c7242b@mail.gmail.com>
	<20090218142057.GA4461@localhost>
Message-ID: <eded84250902191927s55490e06id22eac431854b51e@mail.gmail.com>

On 2/18/09, Chess Griffin <chess at chessgriffin.com> wrote:
> * Mauro Giachero <mauro.giachero at gmail.com> [2009-02-18 10:03:08]:
>> > If that is the case, then instead
>> > of using a tmp file why not have a statement similar to this
>> >
>> > if [ -n "$(diff -q file1 file2 2>/dev/null)" ]; then
>> >  # do_dialog_code
>> > fi
>> >
>> > This would keep y'all from having to manage even more tmp files.
>>
>>
>> But this would to the diff twice...
>> I really think it's a matter of taste here. Frankly, I'm not worried about
>> temp files whose lifespan doesn't exceed that of a single function --
>> after
>> all, it's rather easy to manage them correctly.
>>
>
> I agree.  Let's go with Mauro's patch that leaves the tmp file and includes
> the DIFF and DIFFOPTS variables.
>
> --
> Chess Griffin
>
Leaving the tmp file, etc in is fine.  However, since DIFFOPTS is in
you shouldn't base whether or not to show the dialog by what is in the
tmp file (for instance a DIFFOPTS of '-s' would mess up your logic).
For that I still recommend keeping in the 'diff -q' command similar to
the above (no DIFF or DIFFOPTS used for that one) so that you know
what to expect in the tmp file.

I wouldn't worry about diffing twice, either.  Since with '-q' it is
only checking if there are any differences, the command won't likely
need to compare both files completely unless the worst case scenario
is present (changes at end of file or files identical).  And again,
these are small files, so there shouldn't be a bad lag.

--phillip

From phillip.c.warner at gmail.com  Fri Feb 20 04:47:11 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Thu, 19 Feb 2009 22:47:11 -0600
Subject: [sbopkg-users] sbopkg-renames fix
Message-ID: <eded84250902192047u14c9a95em13d116c1aa970f2b@mail.gmail.com>

The attached patch (for r459) fixes the issue where sbopkg does not
detect (listed at the top)that you have a package installed if it is
using the older name (eg. it says you don't have mplayer installed
when you have MPlayer installed).

The patch also puts the SBOPKG_RENAMES in a couple of spots where it
should already be.

I have not checked yet if there are other renames issues similar to this.

--phillip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: renames-fix.patch
Type: application/octet-stream
Size: 3313 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090219/dff29bb1/attachment.obj>

From phillip.c.warner at gmail.com  Fri Feb 20 04:55:46 2009
From: phillip.c.warner at gmail.com (Phillip Warner)
Date: Thu, 19 Feb 2009 22:55:46 -0600
Subject: [sbopkg-users] Security Issue - TMP files
Message-ID: <eded84250902192055j6b423d9brf1cbd5a4884a92fa@mail.gmail.com>

all of these little temporary files that sbopkg uses to keep track of
itself are not necessarilly in a folder that is owned by root.  This
allows the user that does own TMP (/tmp/SBo by default) to delete and
replace those temporary files with potentially malicious files.

I suggest that TMP be forced to be owned by root.  It should at least
be checked and a clear warning given if it isn't secure.

--phillip

From chess at chessgriffin.com  Fri Feb 20 14:22:28 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Fri, 20 Feb 2009 09:22:28 -0500
Subject: [sbopkg-users] sbopkg-renames fix
In-Reply-To: <eded84250902192047u14c9a95em13d116c1aa970f2b@mail.gmail.com>
References: <eded84250902192047u14c9a95em13d116c1aa970f2b@mail.gmail.com>
Message-ID: <20090220142227.GA7491@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-02-19 22:47:11]:

> The attached patch (for r459) fixes the issue where sbopkg does not
> detect (listed at the top)that you have a package installed if it is
> using the older name (eg. it says you don't have mplayer installed
> when you have MPlayer installed).
> 
> The patch also puts the SBOPKG_RENAMES in a couple of spots where it
> should already be.
> 
> I have not checked yet if there are other renames issues similar to this.
> 

Thanks, Phillip.  I'll queue this one up for review.  We have a lot of
balls in the air as far as development goes, and there are many patches
about to be committed to SVN, so things are moving a lot right now.  But
it looks like this is a good fix, so we'll get to this one as soon as
possible.  Thanks!

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090220/81890e73/attachment.sig>

From chess at chessgriffin.com  Fri Feb 20 14:25:29 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Fri, 20 Feb 2009 09:25:29 -0500
Subject: [sbopkg-users] Security Issue - TMP files
In-Reply-To: <eded84250902192055j6b423d9brf1cbd5a4884a92fa@mail.gmail.com>
References: <eded84250902192055j6b423d9brf1cbd5a4884a92fa@mail.gmail.com>
Message-ID: <20090220142529.GB7491@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-02-19 22:55:46]:

> all of these little temporary files that sbopkg uses to keep track of
> itself are not necessarilly in a folder that is owned by root.  This
> allows the user that does own TMP (/tmp/SBo by default) to delete and
> replace those temporary files with potentially malicious files.
> 
> I suggest that TMP be forced to be owned by root.  It should at least
> be checked and a clear warning given if it isn't secure.

A lot of things will be changing after the next release when we remove
the 'user mode' support and this is one of them.  Stay tuned.  :-)

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090220/11f246e1/attachment.sig>

From chess at chessgriffin.com  Fri Feb 20 14:28:50 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Fri, 20 Feb 2009 09:28:50 -0500
Subject: [sbopkg-users] Install package error checking, options
In-Reply-To: <eded84250902191842r5856888fqc630ad528c8008f0@mail.gmail.com>
References: <eded84250902191842r5856888fqc630ad528c8008f0@mail.gmail.com>
Message-ID: <20090220142850.GC7491@localhost>

* Phillip Warner <phillip.c.warner at gmail.com> [2009-02-19 20:42:40]:

> --- Solution - let the user pick from a list  ---
> What should happen is that the menu should only display that one
> package if it is the only one.  Otherwise, it should display something
> like "choose...", and when you select "install" it should pop up a
> list of all the matching packages with their corresponding 'ls -l'
> output.  The default package selected would ideally be the one that
> matches the build info from the last build for that software.
>

Good idea -- we'll add this to the list.

> --- Minor cleanup on error checking needed ---
> An interesting thing happens if the default package to be installed is
> removed before "install" is selected.  You will get a couple of stat
> errors and then the program complains that the package does not have
> root:root perms (really it has none :)  ).  Then, when it tries to 'ls
> -l' the package there is of course more nasty errors.  If you choose
> to install it, it will obviously fail and no harm seems to be done.
> 

We can work on adding a check there.  Thanks.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090220/43ecd8ea/attachment.sig>

From me at alkos333.net  Sat Feb 21 14:26:55 2009
From: me at alkos333.net (alkos333)
Date: Sat, 21 Feb 2009 08:26:55 -0600
Subject: [sbopkg-users] Client Progress Bars
Message-ID: <a6f13f000902210626h6fa7651ax1e3c6dc1fff47851@mail.gmail.com>

Having progress bars when using client instead of a dialog seems a bit
of an overkill.  I always thought that being able to run sbopkg
without a dialog would be useful if one wanted to pipe the output to
other commands.  IMHO, having progress bars in there, doesn't really
help the cause.

Any thoughts?

-- 

George Burns  - "I would go out with women my age, but there are no
women my age."

From me at alkos333.net  Sat Feb 21 14:38:27 2009
From: me at alkos333.net (alkos333)
Date: Sat, 21 Feb 2009 08:38:27 -0600
Subject: [sbopkg-users] Feature Request
Message-ID: <a6f13f000902210638s5c7a505i87245a6266e5e913@mail.gmail.com>

When one of the packages is updated, I always use the newly added
<String> search (in SVN) to see which other packages might be affected
and need to be recompiled.  The problem is that the entire repository
is searched and sometimes I get quite a long list.  I think it would
be nice to have an option to narrow the search to installed packages
only.

For example, when boost just got updated, I did a <String> search and
found out that Inkscape uses it as well, so I added it to the queue as
well.

What do you think folks?

-- 

P. J. O'Rourke  - "Everybody knows how to raise children, except the
people who have them."

From dave at unrealize.co.uk  Sat Feb 21 17:28:58 2009
From: dave at unrealize.co.uk (Dave Woodfall)
Date: Sat, 21 Feb 2009 17:28:58 +0000
Subject: [sbopkg-users] Feature Request
In-Reply-To: <a6f13f000902210638s5c7a505i87245a6266e5e913@mail.gmail.com>
References: <a6f13f000902210638s5c7a505i87245a6266e5e913@mail.gmail.com>
Message-ID: <20090221172858.GA17927@Junius>

On (08:38 21/02/09), alkos333 <me at alkos333.net> put forth the proposition:
>When one of the packages is updated, I always use the newly added
><String> search (in SVN) to see which other packages might be affected
>and need to be recompiled.  The problem is that the entire repository
>is searched and sometimes I get quite a long list.  I think it would
>be nice to have an option to narrow the search to installed packages
>only.
>
>For example, when boost just got updated, I did a <String> search and
>found out that Inkscape uses it as well, so I added it to the queue as
>well.
>
>What do you think folks?

Sounds reasonable. Something like an 'Installed packages' checkbox?

>
>-- 
>
>P. J. O'Rourke  - "Everybody knows how to raise children, except the
>people who have them."
>_______________________________________________
>sbopkg-users mailing list
>sbopkg-users at sbopkg.org
>http://sbopkg.org/mailman/listinfo/sbopkg-users

-- 
"Ninety percent of the time things turn out worse than you thought they
would.  The other ten percent of the time you had no right to expect
that much."
		-- Augustine
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090221/40f08118/attachment-0001.sig>

From me at alkos333.net  Sat Feb 21 17:33:52 2009
From: me at alkos333.net (alkos333)
Date: Sat, 21 Feb 2009 11:33:52 -0600
Subject: [sbopkg-users] Feature Request
In-Reply-To: <20090221172858.GA17927@Junius>
References: <a6f13f000902210638s5c7a505i87245a6266e5e913@mail.gmail.com>
	<20090221172858.GA17927@Junius>
Message-ID: <a6f13f000902210933s1fbe99f1g4f98120fd781ecd6@mail.gmail.com>

On Sat, Feb 21, 2009 at 11:28 AM, Dave Woodfall <dave at unrealize.co.uk> wrote:
> On (08:38 21/02/09), alkos333 <me at alkos333.net> put forth the proposition:
>>
>> When one of the packages is updated, I always use the newly added
>> <String> search (in SVN) to see which other packages might be affected
>> and need to be recompiled.  The problem is that the entire repository
>> is searched and sometimes I get quite a long list.  I think it would
>> be nice to have an option to narrow the search to installed packages
>> only.
>>
>> For example, when boost just got updated, I did a <String> search and
>> found out that Inkscape uses it as well, so I added it to the queue as
>> well.
>>
>> What do you think folks?
>
> Sounds reasonable. Something like an 'Installed packages' checkbox?
>

Yes, something similar to that, so that instead of searching the
entire repository for the string specified, it would just search only
within the installed packages.


-- 

George Burns  - "I would go out with women my age, but there are no
women my age."

From me at alkos333.net  Mon Feb 23 23:38:20 2009
From: me at alkos333.net (alkos333)
Date: Mon, 23 Feb 2009 17:38:20 -0600
Subject: [sbopkg-users] r478 and Searchby Installed Packages
Message-ID: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>

I don't see how I can search by installed packages in r478?

From me at alkos333.net  Mon Feb 23 23:39:25 2009
From: me at alkos333.net (alkos333)
Date: Mon, 23 Feb 2009 17:39:25 -0600
Subject: [sbopkg-users] r478 and Searchby Installed Packages
In-Reply-To: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>
References: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>
Message-ID: <a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>

Never mind, just had to read the HELP... but  it would be nice if this
somehow could be integrated in the UI.

On Mon, Feb 23, 2009 at 5:38 PM, alkos333 <me at alkos333.net> wrote:
> I don't see how I can search by installed packages in r478?
>

From chess at chessgriffin.com  Tue Feb 24 00:34:03 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 23 Feb 2009 19:34:03 -0500
Subject: [sbopkg-users] r478 and Searchby Installed Packages
In-Reply-To: <a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>
References: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>
	<a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>
Message-ID: <20090224003402.GA22060@localhost>

* alkos333 <me at alkos333.net> [2009-02-23 17:39:25]:

> Never mind, just had to read the HELP... but  it would be nice if this
> somehow could be integrated in the UI.
> 

How about something like the attached diff?

-- 
Chess Griffin
-------------- next part --------------
Index: src/usr/bin/sbopkg
===================================================================
--- src/usr/bin/sbopkg	(revision 479)
+++ src/usr/bin/sbopkg	(working copy)
@@ -2803,7 +2803,9 @@
         dialog --title "Search" --ok-label "PKG" \
             --extra-button --extra-label "String" \
             --help-button --inputbox \
-            "Enter your search term..." 8 39 2> $TERM_FILE
+            "Enter your search term (prefix your search with 'inst:' \
+                to narrow search to installed packages)..." 10 39 \
+                2> $TERM_FILE
         case $? in # 0=PKG 3=String 1=Cancel 2=Help
             3) STRING=yes ;;
             2) dialog --title "Search Help" --msgbox \
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090223/1f093916/attachment.sig>

From jsunx1 at bellsouth.net  Tue Feb 24 00:43:37 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Mon, 23 Feb 2009 19:43:37 -0500
Subject: [sbopkg-users] r478 and Searchby Installed Packages
In-Reply-To: <a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>
References: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>
	<a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>
Message-ID: <20090224004337.GB27167@surfandslam>

On 2009-02-23 (Mon) 17:39:25 [-0600], alkos333 wrote:
> Never mind, just had to read the HELP... but  it would be nice if this
> somehow could be integrated in the UI.
> 

I agree, but the problem is a limitation with dialog - only two buttons
can pass useful data (and are already used for PKG and String) and using
another widget would have required a larger restructuring than I was
prepared to do at this point. Also, there aren't many good options even
among the other widget types. Nested widgets are another option but I
try to avoid that as much as possible. In this case, it'd be an extra
step for what I suspect is the majority of use cases where someone just
wants to search all packages.

Still, it's possible it'll be reworked in the future and, if you have
any suggestions or encounter any problems with the current
implementation, post 'em up.

From jsunx1 at bellsouth.net  Tue Feb 24 00:59:47 2009
From: jsunx1 at bellsouth.net (slakmagik)
Date: Mon, 23 Feb 2009 19:59:47 -0500
Subject: [sbopkg-users] r478 and Searchby Installed Packages
In-Reply-To: <20090224003402.GA22060@localhost>
References: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>
	<a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>
	<20090224003402.GA22060@localhost>
Message-ID: <20090224005947.GC27167@surfandslam>

On 2009-02-23 (Mon) 19:34:03 [-0500], Chess Griffin wrote:
> * alkos333 <me at alkos333.net> [2009-02-23 17:39:25]:
> 
> > Never mind, just had to read the HELP... but  it would be nice if this
> > somehow could be integrated in the UI.
> > 
> 
> How about something like the attached diff?
> 
> -- 
> Chess Griffin

> Index: src/usr/bin/sbopkg
> ===================================================================
> --- src/usr/bin/sbopkg	(revision 479)
> +++ src/usr/bin/sbopkg	(working copy)
> @@ -2803,7 +2803,9 @@
>          dialog --title "Search" --ok-label "PKG" \
>              --extra-button --extra-label "String" \
>              --help-button --inputbox \
> -            "Enter your search term..." 8 39 2> $TERM_FILE
> +            "Enter your search term (prefix your search with 'inst:' \
> +                to narrow search to installed packages)..." 10 39 \
> +                2> $TERM_FILE
>          case $? in # 0=PKG 3=String 1=Cancel 2=Help
>              3) STRING=yes ;;
>              2) dialog --title "Search Help" --msgbox \

Oh, put *that* in the UI. Yeah, that can be done. :)

From me at alkos333.net  Tue Feb 24 03:06:47 2009
From: me at alkos333.net (alkos333)
Date: Mon, 23 Feb 2009 21:06:47 -0600
Subject: [sbopkg-users] r478 and Searchby Installed Packages
In-Reply-To: <20090224005947.GC27167@surfandslam>
References: <a6f13f000902231538i15ec515at559c71a5461cff5@mail.gmail.com>
	<a6f13f000902231539s3c59ca99r69d06b85a813883a@mail.gmail.com>
	<20090224003402.GA22060@localhost>
	<20090224005947.GC27167@surfandslam>
Message-ID: <a6f13f000902231906o403a84a6ya152a5b729058fb6@mail.gmail.com>

On Mon, Feb 23, 2009 at 6:59 PM, slakmagik <jsunx1 at bellsouth.net> wrote:
> On 2009-02-23 (Mon) 19:34:03 [-0500], Chess Griffin wrote:
>> * alkos333 <me at alkos333.net> [2009-02-23 17:39:25]:
>>
>> > Never mind, just had to read the HELP... but  it would be nice if this
>> > somehow could be integrated in the UI.
>> >
>>
>> How about something like the attached diff?
>>
>> --
>> Chess Griffin
>
>> Index: src/usr/bin/sbopkg
>> ===================================================================
>> --- src/usr/bin/sbopkg        (revision 479)
>> +++ src/usr/bin/sbopkg        (working copy)
>> @@ -2803,7 +2803,9 @@
>>          dialog --title "Search" --ok-label "PKG" \
>>              --extra-button --extra-label "String" \
>>              --help-button --inputbox \
>> -            "Enter your search term..." 8 39 2> $TERM_FILE
>> +            "Enter your search term (prefix your search with 'inst:' \
>> +                to narrow search to installed packages)..." 10 39 \
>> +                2> $TERM_FILE
>>          case $? in # 0=PKG 3=String 1=Cancel 2=Help
>>              3) STRING=yes ;;
>>              2) dialog --title "Search Help" --msgbox \
>
> Oh, put *that* in the UI. Yeah, that can be done. :)
> _______________________________________________
> sbopkg-users mailing list
> sbopkg-users at sbopkg.org
> http://sbopkg.org/mailman/listinfo/sbopkg-users
>

This is definitely better.

-- 

Vince Lombardi  - "Winning is habit. Unfortunately, so is losing."

From chess at chessgriffin.com  Wed Feb 25 02:35:07 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 24 Feb 2009 21:35:07 -0500
Subject: [sbopkg-users] Upcoming Release
Message-ID: <20090225023507.GA2860@localhost>

We are getting very near a new release of sbopkg, and there are lots of
new features and improvements.  I would greatly appreciate it folks
could test it either by pulling from SVN directly or using slakmagik's
nifty 'sspm' utility.  If you have a chance to test and come across any
bugs or issues, please post them here to the list or feel free to send
me an email.

Thanks!

-- 
Chess Griffin

From chess at chessgriffin.com  Thu Feb 26 15:21:40 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 26 Feb 2009 10:21:40 -0500
Subject: [sbopkg-users] Sbopkg 0.27.0 released
Message-ID: <20090226152140.GA18127@localhost>

A new version 0.27.0 of sbopkg has been released.  Once again, I have
had great assistance from several contributors in the form of feature
requests, bug reports, and patches.  I would like to especially thank
Mauro Giachero and slakmagik for their hard work in reviewing code,
providing patches, and offering excellent advice and suggestions.

This release brings many bug fixes and new features.  Please be aware
that there are some new variables for sbopkg.conf, so if you are
upgrading, be sure to check out the sbopkg.conf.new and merge the
changes.

Here are a few of the notable items from the ChangeLog.txt:

  * Commit a patch that adds a new sbopkg.conf configuration variable,
    QUEUEDIR, where users can define where saved queues are stored; also, when
    the user wants to load a saved queue, show a list of available saved
    queues; thanks to slakmagik for the patch.
  * Add ability to search for keywords in the README files using regular
    expressions; this new 'string search' can also be narrowed to only search
    installed packages; thanks to slakmagik for the original patch and
    implementation and thanks to both slakmagik and Mauro Giachero for
    cleaning it up and addressing minor issues before the commit.
  * Add ability to view a diff of an edited .info or SlackBuild file before
    choosing which one to use; this feature adds two configuration variables
    to the sbopkg.conf file: DIFF and DIFFOPTS; thanks to Phillip Warner for
    the suggestion and thanks to Mauro Giachero for helping debug/improve my
    original implemenation.
  * Add ability to view more files in each application's folder, i.e.
    doinst.sh, or *.desktop files; thanks to Phillip Warner for the suggestion
    and thanks to slakmagik for the patch implementing this feature.
  * Rework the check for root:root permissions when installing packages; now,
    if the package does not have root:root permissions, sbopkg will display
    the output of ls -l <packagename> and ask if the user wishes to install or
    abort, rather than only aborting.
  * Move the -q option to -g (general search) in order to make way for -q,
    'quiet mode' where the output of some of the command line options (i.e.
    the command line progressbar) can be minimized.  More quieting will likely
    occur in future releases.  Thanks to alkos333 for the feature request.
  * Implement a workaround so that the dialog interface now works better with
    GNU Screen and rxvt-based terminals. Thanks to Phillip Warner for raising
    the issue and thanks to Mauro Giachero for working on the implementation.
  * Include a French translation of the two sbopkg man pages.  For now, these
    man pages will be included in the /doc directory until I have time to
    figure out whether they can be automatically installed in place of the
    English ones depending on a locale setting.  In any event, I would like to
    extend my thanks to Marie-Claude Collilieux for providing this first
    translation for sbopkg.  I am sure folks will appreciate the work she put
    into it.  If anyone else wants to follow her lead and provide some other
    translations, I would be happy to include them.  Thanks Marie-Claude!
  * Add in several patches from slakmagik that lets the user choose from saved
    queues, modifies how the saved queues and backup queues work, and modifies
    several other queue-related functions and menus.  Many thanks to slakmagik
    for his continually excellent contributions.
  * Implement an 'autoqueue' by allowing the user to specify queue names to
    '-b' and '-i' and by adding a -e option whereby the user can specify what
    to do on errors (stop, ask, or continue).  Thanks to Alan Hicks for
    suggesting this feature and thanks to Mauro Giachero for the
    implementation.

The full ChangeLog.txt can be read here:
http://www.sbopkg.org/files/ChangeLog.txt

So, to recap, there are three new variables for sbopkg.conf:
QUEUEDIR, DIFF, and DIFFOPTS.  These are explained in the sbopkg.conf(5)
man page and need to be added to your current sbopkg.conf if you are
upgrading.

A noarch package and source tarball for version 0.27.0 can be found at
the sbopkg project website:

http://www.sbopkg.org

I would also like to make an important announcement about upcoming
versions of sbopkg.  Now that 0.27.0 is out the door, we are going to
take some time off, and then turn our attention to an overall code
review/audit with an eye towards making the code more efficient with
less bugs.  It is unlikely that new features will be implemented.  Along
with this review, we will be removing the 'user mode' support from
sbopkg and changing the codebase so sbopkg runs out of /usr/sbin and
requires root privileges, just like several other similar Slackware
package tools.  Additionally, we will be reviewing the file and
directory layout for sbopkg-related items to consider whether things
need to be moved.  Personally, I am leaning towards moving everything
into /var/lib/sbopkg, so there would be
/var/lib/sbopkg/{repo,tmp,cache,queues} etc., but we have not spent much
time discussing this.  If you have any thoughts on what would be a set
of sensible defaults in this area, please feel free to speak up.
Obviously, if the directory structure is moved, this will require future
user intervention in the form of moving your local repo, or adjusting
the sbopkg.conf back to where you want things to be stored.

Anyway, the point here is simply to let folks know what is on the
horizon for future releases.  There is no timetable for when the post
0.27.0 release will occur, but this next major release will probably
take longer than past releases.  I have created a 0.27.0-stable branch
in SVN so we can backport fixes and address issues in the 0.27.0
release as they come up.

Again, I would like to thank all the contributors to sbopkg.  This
utility is greatly benefiting from the feedback and assistance of many
individuals.

Enjoy!

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090226/791e88d4/attachment-0001.sig>

From rworkman at slackbuilds.org  Thu Feb 26 16:48:39 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 26 Feb 2009 10:48:39 -0600
Subject: [sbopkg-users] [Slackbuilds-users]  Sbopkg 0.27.0 released
In-Reply-To: <20090226104549.5d675767@liberty.rlwhome.lan>
References: <20090226152140.GA18127@localhost>
	<20090226104549.5d675767@liberty.rlwhome.lan>
Message-ID: <20090226104839.60be09e9@liberty.rlwhome.lan>

On Thu, 26 Feb 2009 10:45:49 -0600
Robby Workman <rw at rlworkman.net> wrote:

> On Thu, 26 Feb 2009 10:21:40 -0500
> Chess Griffin <chess at chessgriffin.com> wrote:
> 
> >   * Include a French translation of the two sbopkg man pages.  For
> > now, these man pages will be included in the /doc directory until I
> > have time to figure out whether they can be automatically installed
> > in place of the English ones depending on a locale setting. 
> 
> 
> Install them to /usr/man/fr/man?/
> 
> See attached patch.


Er, ignore the patch.  svn's diff implementation when files are moved
around seems to be braindead.

Basically, there was just some usage of svn mkdir and svn mv to
accomplish what I hope is obvious at this point.  If not, let me
know.   :-)

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090226/1f7c352e/attachment.asc>

From rw at rlworkman.net  Thu Feb 26 16:45:49 2009
From: rw at rlworkman.net (Robby Workman)
Date: Thu, 26 Feb 2009 10:45:49 -0600
Subject: [sbopkg-users] Sbopkg 0.27.0 released
In-Reply-To: <20090226152140.GA18127@localhost>
References: <20090226152140.GA18127@localhost>
Message-ID: <20090226104549.5d675767@liberty.rlwhome.lan>

On Thu, 26 Feb 2009 10:21:40 -0500
Chess Griffin <chess at chessgriffin.com> wrote:

>   * Include a French translation of the two sbopkg man pages.  For
> now, these man pages will be included in the /doc directory until I
> have time to figure out whether they can be automatically installed
> in place of the English ones depending on a locale setting. 


Install them to /usr/man/fr/man?/

See attached patch.


> /var/lib/sbopkg/{repo,tmp,cache,queues} etc., but we have not spent
> much time discussing this.  If you have any thoughts on what would be
> a set of sensible defaults in this area, please feel free to speak up.


Unless moving to a more self-contained layout simplifies things for
you, I wouldn't do it that way.  I'd lean more toward using these:
  /var/tmp/sbopkg
  /var/cache/sbopkg
  /var/lib/sbopkg/{queues,repo}
  Other things might belong in subdirs of /var/{tmp,cache}/sbopkg as
  appopriate, and probably other things (stuff you want to keep around
  no matter what) will go in /var/lib/sbopkg.  Anyway, hopefully that
  made a little bit of sense... :-)

-RW
  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: install_fr_manpages.diff
Type: text/x-patch
Size: 14937 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090226/ea20bbb6/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20090226/ea20bbb6/attachment.asc>