From eric at schultzter.ca Fri Feb 10 05:39:20 2012 From: eric at schultzter.ca (Eric Schultz) Date: Fri, 10 Feb 2012 00:39:20 -0500 Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root Message-ID: Good evening... Sorry to re-open an old and probably closed discussion but I have a pertinent situation. Perhaps there's something I'm not understanding, but I want to do is have my server (a NAS) rsync the SlackBuilds.org repository so it's available to all my computers. Rather than have each one sync the repository themselves. I know it's not much data but it seems much more efficient to only do it once. As such, I wanted to set the REPO_ROOT to an NFS mounted directory from my server. And of course the REPO_NAME and REPO_BRANCH appropriately too. But sbopkg is checking to see if it has write-access to the directory, which it doesn't. Normally root won't on an NFS mounted share (security/paranoia, that kind of thing). So it fails, right from the start. Except it should never have to write to the directory since my server is taking care of keeping the local copy up-to-date. I've done some bash scripting, so I could probably contribute but is this already possible with some option I've missed? Or is there some "gotcha" that will make this difficult or impossible to implement? Thanks, BTW, is there a searchable archive for sbopkg-users? I couldn't find anything on gmane or marc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Fri Feb 10 05:56:17 2012 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Fri, 10 Feb 2012 10:56:17 +0500 Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root In-Reply-To: References: Message-ID: 2012/2/10 Eric Schultz > Good evening... > > But sbopkg is checking to see if it has write-access to the directory, > which it doesn't. Normally root won't on an NFS mounted share > (security/paranoia, that kind of thing). So it fails, right from the start. > > Except it should never have to write to the directory since my server is > taking care of keeping the local copy up-to-date. > sbopkg creates a syslink from source tarball in cache folder to the folder where the script is (in the repo). That's where it needs write access in the first place and secondly Bild sciprt itself may need it as well for some reason. -- Ozan, BSc, BEng -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Fri Feb 10 06:06:49 2012 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 10 Feb 2012 00:06:49 -0600 Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root In-Reply-To: References: Message-ID: <20120210000649.5b0c790d@shaggy.doo> On Fri, 10 Feb 2012 00:39:20 -0500 Eric Schultz wrote: > Except it should never have to write to the directory since my server > is taking care of keeping the local copy up-to-date. It's doing this because it symlinks the source tarball into the repo directory. This is not behavior I agree with. > I've done some bash scripting, so I could probably contribute but is > this already possible with some option I've missed? Or is there some > "gotcha" that will make this difficult or impossible to implement? The fix here is to not do what I mentioned above. It should be working in $TMPDIR at all times. -- Erik Hanson From eric at schultzter.ca Fri Feb 10 17:33:21 2012 From: eric at schultzter.ca (Eric Schultz) Date: Fri, 10 Feb 2012 12:33:21 -0500 Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root Message-ID: > > > 2012/2/10 Eric Schultz >> But sbopkg is checking to see if it has write-access to the directory, >> which it doesn't. Normally root won't on an NFS mounted share >> (security/paranoia, that kind of thing). So it fails, right from the start. > > > Except it should never have to write to the directory since my server is >> taking care of keeping the local copy up-to-date. > > > sbopkg creates a syslink from source tarball in cache folder to the folder > where the script is (in the repo). That's where it needs write access in > the first place and secondly Bild sciprt itself may need it as well for > some reason. Good evening... > > -- > Ozan, BSc, BEng Ah! I see, that answers that question then. I guess what I can do is sync SBo to my NAS and then sync my computers from there. Although I was considering using ponce's -current repository (since I just upgraded to -current) and that requires git, which my NAS doesn't do. Thanks, 2012/2/10 > Send sbopkg-users mailing list submissions to > sbopkg-users at sbopkg.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://sbopkg.org/mailman/listinfo/sbopkg-users > or, via email, send a message with subject or body 'help' to > sbopkg-users-request at sbopkg.org > > You can reach the person managing the list at > sbopkg-users-owner at sbopkg.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sbopkg-users digest..." > > Today's Topics: > > 1. Re: Using http, Curl as a repository tool (slakmagik) > 2. Re: Using http, Curl as a repository tool (Asaf) > 3. Finding Help with GnuCash (jamesgilmour) > 4. Re: Finding Help with GnuCash (Mauro Giachero) > 5. Re: Finding Help with GnuCash (Pierre Cazenave) > 6. Moving sbopkg to /usr/sbin and require root (Eric Schultz) > 7. Re: Moving sbopkg to /usr/sbin and require root (Ozan T?rky?lmaz) > > > ---------- Forwarded message ---------- > From: slakmagik > To: sbopkg-users at sbopkg.org > Cc: > Date: Wed, 3 Aug 2011 19:19:07 -0400 > Subject: Re: [sbopkg-users] Using http, Curl as a repository tool > On 2011-08-03 (Wed) 23:18:21 [+0300], Asaf wrote: > > Continued from: > > http://sbopkg.org/pipermail/sbopkg-users/2010-July/000492.html > > > > I've forked sbopkg to implement Curl repository tool: > > https://github.com/asafo/sbopkg > > > > there is also a sample repos.d/80-SBo-curl.repo > > > > I'll be happy for any suggestions to help it get merged > > > > First, am I to understand that every use of 'sbopkg -r' using this would > result in downloading the entire SBo repository? Because I don't think > that's acceptable, both from a user's POV and from the SBo admin's POV. > > For less major points: your 80 repo file doesn't work because it > attempts to sync to localhost. Even after correcting that to a full url, > the protocol is duplicated in _curl_sync_package(). Even after > correcting that, gunzip asks about whether it should overwrite > SLACKBUILDS.TXT if that file already exists. > > For relatively minor points, we don't use the _func convention (not > saying whether we should or not, but we don't) and your patches have > trailing whitespace. Also we only use the '['-style test on pathnames > and maybe not always then. We prefer '[[' for strings and '((' for > numerics. We don't leave commented-out code in (if we do, it's a > mistake). Error messages should announce that they're coming from > $SCRIPT (and I don't mind even $FUNCNAME at times). While there's > nothing in writing about and sbopkg is very bashistic, I'd personally > still prefer to avoid stuff like BASH_REMATCH, though the use is really > spiffy in this case and might well be the best thing to do. I'm not fond > of _curl_fail() when it's only used once and its functionality could > just be used directly in the _curl_sync_package() line where it's > called. And I'm personally a <80 columns fanatic. Lines should fit > within standard terminal widths wherever possible. > > Lastly, a major point, I'd raise first except that I wouldn't document > something until I knew it was going in, myself, but anything that would > go in would have to be thoroughly documented (man pages, always, and any > relevant text files). > > Well, lastly lastly, I've only briefly looked at the patches (or patch, > as it could be profitably 'squashed' into one, IMO) and only briefly > tested but, while I'm testing, I'm noticing a lot of hangs and 'Curl > Failed: 6's so this doesn't seem very efficient and effective even > without the non-differencing problem. > > But, other than these points, it's pretty neat. I definitely appreciate > your interest and this contribution but, if I understand it correctly, I > don't think I'm in favor of it, at least at this point. We really do > intend to get an lftp sync method in soon and, while that's not http, it > might help with some people who have rsync issues while still only > updating the differences. Or possibly something could be worked out via > parsing the ChangeLog and only http'ing those packages. > > But maybe if Mauro's around, he'll have a different take. > > And, yeah, the http sync is still ongoing after having been started > before I began this email (and I take forever with emails). ;) > > > > ---------- Forwarded message ---------- > From: Asaf > To: sbopkg-users at sbopkg.org > Cc: > Date: Thu, 04 Aug 2011 10:32:49 +0300 > Subject: Re: [sbopkg-users] Using http, Curl as a repository tool > On 08/04/2011 02:19 AM, slakmagik wrote: > >> On 2011-08-03 (Wed) 23:18:21 [+0300], Asaf wrote: >> >>> Continued from: >>> http://sbopkg.org/pipermail/**sbopkg-users/2010-July/000492.**html >>> >>> I've forked sbopkg to implement Curl repository tool: >>> https://github.com/asafo/**sbopkg >>> >>> there is also a sample repos.d/80-SBo-curl.repo >>> >>> I'll be happy for any suggestions to help it get merged >>> >>> First, am I to understand that every use of 'sbopkg -r' using this would >> result in downloading the entire SBo repository? Because I don't think >> that's acceptable, both from a user's POV and from the SBo admin's POV. >> > Yes, the work is not complete yet, there are starting points for parsing > the ChangeLog.txt file (Actually, the diff with the old ChangleLog.txt, if > there is one) > so that only new packages would get downloaded > > For less major points: your 80 repo file doesn't work because it >> attempts to sync to localhost. Even after correcting that to a full url, >> the protocol is duplicated in _curl_sync_package(). Even after >> correcting that, gunzip asks about whether it should overwrite >> SLACKBUILDS.TXT if that file already exists. >> > This is going to change, when ChangeLog.txt parsing implementation is > complete, > also, there is currently no public repository available (I hope that they > will open one at > slackbuilds.org), so I'm using localhost for testing > >> >> For relatively minor points, we don't use the _func convention (not >> saying whether we should or not, but we don't) and your patches have >> trailing whitespace. Also we only use the '['-style test on pathnames >> and maybe not always then. We prefer '[[' for strings and '((' for >> numerics. We don't leave commented-out code in (if we do, it's a >> mistake). Error messages should announce that they're coming from >> $SCRIPT (and I don't mind even $FUNCNAME at times). While there's >> nothing in writing about and sbopkg is very bashistic, I'd personally >> still prefer to avoid stuff like BASH_REMATCH, though the use is really >> spiffy in this case and might well be the best thing to do. I'm not fond >> of _curl_fail() when it's only used once and its functionality could >> just be used directly in the _curl_sync_package() line where it's >> called. And I'm personally a<80 columns fanatic. Lines should fit >> within standard terminal widths wherever possible. >> > the use of BASH_REMATCH saves a lot of process forking (grep, cut, sed, > etc..) > (or is there a third way ?) > >> >> Lastly, a major point, I'd raise first except that I wouldn't document >> something until I knew it was going in, myself, but anything that would >> go in would have to be thoroughly documented (man pages, always, and any >> relevant text files). >> >> Well, lastly lastly, I've only briefly looked at the patches (or patch, >> as it could be profitably 'squashed' into one, IMO) and only briefly >> tested but, while I'm testing, I'm noticing a lot of hangs and 'Curl >> Failed: 6's so this doesn't seem very efficient and effective even >> without the non-differencing problem. >> >> But, other than these points, it's pretty neat. I definitely appreciate >> your interest and this contribution but, if I understand it correctly, I >> don't think I'm in favor of it, at least at this point. We really do >> intend to get an lftp sync method in soon and, while that's not http, it >> might help with some people who have rsync issues while still only >> updating the differences. Or possibly something could be worked out via >> parsing the ChangeLog and only http'ing those packages. >> > lftp wouldn't solve the problem (restrictive firewalls) > >> >> But maybe if Mauro's around, he'll have a different take. >> >> And, yeah, the http sync is still ongoing after having been started >> before I began this email (and I take forever with emails). ;) >> ______________________________**_________________ >> sbopkg-users mailing list >> sbopkg-users at sbopkg.org >> http://sbopkg.org/mailman/**listinfo/sbopkg-users >> >> > > -- > Asaf Ohaion > Lingnu Open Source Consulting Ltd > http://www.lingnu.com > > > > > ---------- Forwarded message ---------- > From: jamesgilmour > To: > Cc: > Date: Wed, 19 Oct 2011 17:38:04 +1100 > Subject: [sbopkg-users] Finding Help with GnuCash > Hi, > I have downloaded GnuCash with sbopkg;when I try to open "Help" > - Contents I get the error message '"help" not available, this > is probably because "gnucash-docs" is not installed.' > As 'GnuCash-docs' is not available in the sbopkg repository, > what must I do to find it? > > -- > James&Helen > > > > ---------- Forwarded message ---------- > From: Mauro Giachero > To: Sbopkg Users List > Cc: > Date: Wed, 19 Oct 2011 17:23:41 +0200 > Subject: Re: [sbopkg-users] Finding Help with GnuCash > On Wed, Oct 19, 2011 at 08:38, jamesgilmour wrote: > >> Hi, >> > > Hi > > >> I have downloaded GnuCash with sbopkg;when I try to open "Help" >> - Contents I get the error message '"help" not available, this >> is probably because "gnucash-docs" is not installed.' >> As 'GnuCash-docs' is not available in the sbopkg repository, >> what must I do to find it? >> > > You should ask to the gnucash maintainer (his mail is available in the > gnucash page on SBo, see [1]). Your problem is very gnucash-specific, and > sbopkg doesn't know much about the packages it builds. > > -- >> James&Helen >> > > [1] http://slackbuilds.org/repository/13.37/business/gnucash/ > > Regards > -- > Mauro Giachero > > > ---------- Forwarded message ---------- > From: Pierre Cazenave > To: Sbopkg Users List > Cc: > Date: Wed, 19 Oct 2011 17:15:09 +0100 > Subject: Re: [sbopkg-users] Finding Help with GnuCash > > > On 19/10/2011 07:38, jamesgilmour wrote: > >> Hi, >> I have downloaded GnuCash with sbopkg;when I try to open "Help" >> - Contents I get the error message '"help" not available, this >> is probably because "gnucash-docs" is not installed.' >> As 'GnuCash-docs' is not available in the sbopkg repository, >> what must I do to find it? >> >> > Either someone will have to submit a script to build it [0], or you can > use the online version: > > http://code.gnucash.org/docs/**help/help.html > > Pierre > > [0] http://sourceforge.net/**projects/gnucash/files/**gnucash-docs/2.4.1/ > > > > ---------- Forwarded message ---------- > From: Eric Schultz > To: sbopkg-users at sbopkg.org > Cc: > Date: Fri, 10 Feb 2012 00:39:20 -0500 > Subject: [sbopkg-users] Moving sbopkg to /usr/sbin and require root > Good evening... > > Sorry to re-open an old and probably closed discussion but I have a > pertinent situation. > > Perhaps there's something I'm not understanding, but I want to do is have > my server (a NAS) rsync the SlackBuilds.org repository so it's available to > all my computers. Rather than have each one sync the repository themselves. > I know it's not much data but it seems much more efficient to only do it > once. > > As such, I wanted to set the REPO_ROOT to an NFS mounted directory from my > server. And of course the REPO_NAME and REPO_BRANCH appropriately too. > > But sbopkg is checking to see if it has write-access to the directory, > which it doesn't. Normally root won't on an NFS mounted share > (security/paranoia, that kind of thing). So it fails, right from the start. > > Except it should never have to write to the directory since my server is > taking care of keeping the local copy up-to-date. > > I've done some bash scripting, so I could probably contribute but is this > already possible with some option I've missed? Or is there some "gotcha" > that will make this difficult or impossible to implement? > > Thanks, > > BTW, is there a searchable archive for sbopkg-users? I couldn't find > anything on gmane or marc. > > > > > > ---------- Forwarded message ---------- > From: "Ozan T?rky?lmaz" > To: Sbopkg Users List > Cc: > Date: Fri, 10 Feb 2012 10:56:17 +0500 > Subject: Re: [sbopkg-users] Moving sbopkg to /usr/sbin and require root > 2012/2/10 Eric Schultz > >> Good evening... >> >> But sbopkg is checking to see if it has write-access to the directory, >> which it doesn't. Normally root won't on an NFS mounted share >> (security/paranoia, that kind of thing). So it fails, right from the start. >> >> Except it should never have to write to the directory since my server is >> taking care of keeping the local copy up-to-date. >> > > sbopkg creates a syslink from source tarball in cache folder to the folder > where the script is (in the repo). That's where it needs write access in > the first place and secondly Bild sciprt itself may need it as well for > some reason. > > > -- > Ozan, BSc, BEng > > > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bradley at NorthTech.US Fri Feb 24 16:10:32 2012 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Fri, 24 Feb 2012 08:10:32 -0800 Subject: [sbopkg-users] OMDistro questions... Message-ID: <4F47B678.8050208@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I looked and didn't see OMDistro in the SBo repo. I'm wondering if this would be a problematic thing, and if not. I might try and create an SBo for it. I'm concerned that it might cause conflicts of some sort or another. Your thoughts? - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJPR7Z3AAoJEE1wgkIhr9j3kRYH/2+dw2dlwZdzV820G+j7A1tJ 15DIqhlJwYqEXCCk7jcuC4Aa79fNkbz4PPBxzb0h4w2uUb8r0GfLUAhVCSnblLFk iz6s4EwbC3lI/W34ibHZqUO/ZlMTDyY5brK2NtYaVytEiLzAr4KTOzfP73HJgDRu x5MNM7kqqs7zCdtU3I7be/QTPnX1Gx2304lJW37cO+dM2Zk0TJCoPynGITb4B7iL DxHCIPyi8l2+fvj0UF1hNu2ngCwLYgb7K5OanPDZjfQIivrT8ilEusDeq47QfC4I 4o+73pVjRlaTh+Lu5QUsjxzcdrYrOCn2THfCfb729gHQq5BAmtWQKVAm83HEcug= =W9yF -----END PGP SIGNATURE----- From Bradley at NorthTech.US Fri Feb 24 23:46:40 2012 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Fri, 24 Feb 2012 15:46:40 -0800 Subject: [sbopkg-users] New old version of twin is finally up... Message-ID: <4F482160.7070200@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hey I've been really advocating the use of Twin for some time now. It's better, IMO, than VWM, and VWM is, IMO, better than Twin - it just depends on which feature set I want to use at the moment I guess. Anyway, for over a year now, version 0.6.2 has been available, but it was at Max's old University site and not sourceforge. I gave him a nudge after sending the SBo maintainer an email pointing to the newest version but never heard anything back. Mathhew might have had a lot on his plate at the time. That was fine until one day the original home site for Twin was taken offline and the new version wasn't up at sourceforge (0.6.1 was the latest there), so I went to task and Max just uploaded the 0.6.2 version. If anyone is so inclined, I've maintained the x86_64 version of the packages, 0.6.2 being at: gopher://gopher.northtech.us/9/software/packages/twin-0.6.2-x86_64-1_SBo.tgz but I wouldn't mind at all if Matthew wanted me to take over the SlackBuild for Twin, considering it's been such a pet project for me over the past few years anyway - hint hint :) I truly believe this is a VERY underutilized tool. Anyway, I've BCC'd him on this, seeing how he's the maintainer, and whichever way he would like to go on this would be great for the community I'm sure. Apologies for being somewhat off-topic if anyone found this post bothersome. Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJPSCFfAAoJEE1wgkIhr9j3wkIH/RrLkB/Tu7RQRWRkuhYIhTIy ntMf+bB3KZ2Hh5rkB3GdkXSnlrZwS4dkI2Osy63Dh6F8r+UaxMw3nRzYbhXOCdH/ YjefM9ztY7FQe9fW0QQot0desindNPAZU9gXWk2KxQyMPnw0CekcyH79+RUu+7L5 6jA6ubBdKyBZzH9Pog/vjBAUZlB9Gs4346syEkptq/SpFFedKpwiaXxOrkIoJf++ J76GBQ6x+cpgobqI167C+YVXifKu4fKdgQs3V8ptxquagM5gkQ1wopFdIyJZ+f+s fs5k9aK/RVkQZTtB2XLqKojq+7hT4G9JQO32JJtTh8hjm09Y4ZT9VlC67xSqUvw= =wEKX -----END PGP SIGNATURE----- From Bradley at NorthTech.US Sat Feb 25 00:51:54 2012 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Fri, 24 Feb 2012 16:51:54 -0800 Subject: [sbopkg-users] New old version of twin is finally up... In-Reply-To: <4F482160.7070200@NorthTech.US> References: <4F482160.7070200@NorthTech.US> Message-ID: <4F4830AA.5030106@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Oh Man... Talk about a boner. My Bad for the post below. I set up nickname shortcuts for lists and people I email regularly, and thought that 'sbo' went to the SlackBuilds list. Please accept my apologies for the *der* posting :( On 02/24/2012 03:46 PM, Bradley D. Thornton wrote: > Hey I've been really advocating the use of Twin for some time now. It's > better, IMO, than VWM, and VWM is, IMO, better than Twin - it just > depends on which feature set I want to use at the moment I guess. > > Anyway, for over a year now, version 0.6.2 has been available, but it > was at Max's old University site and not sourceforge. I gave him a nudge > after sending the SBo maintainer an email pointing to the newest version > but never heard anything back. Mathhew might have had a lot on his plate > at the time. > > That was fine until one day the original home site for Twin was taken > offline and the new version wasn't up at sourceforge (0.6.1 was the > latest there), so I went to task and Max just uploaded the 0.6.2 version. > > If anyone is so inclined, I've maintained the x86_64 version of the > packages, 0.6.2 being at: > gopher://gopher.northtech.us/9/software/packages/twin-0.6.2-x86_64-1_SBo.tgz > but I wouldn't mind at all if Matthew wanted me to take over the > SlackBuild for Twin, considering it's been such a pet project for me > over the past few years anyway - hint hint :) > > I truly believe this is a VERY underutilized tool. > > Anyway, I've BCC'd him on this, seeing how he's the maintainer, and > whichever way he would like to go on this would be great for the > community I'm sure. > > Apologies for being somewhat off-topic if anyone found this post bothersome. > > Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJPSDCqAAoJEE1wgkIhr9j365AH/1xsDIQlyFfYXXxOGXWoyzUC zx6QbtywwdgLUVVbumAHhXogTI5+bW4XYB5Lr+F/ZLDQZkvJLnC/Y8ccxOA7iGQi LBhNZL6hJcd+VSMxaYBowpLLtWPhxYiT7R9pVWctJWXhqMHzf2vy803gIQqBjbX1 Cg5ZvMb1LAGFmzK2OgA4KYgSFNQK6f3ElCUQhu7sfBKXwQKCOtcWK5j1zDTh/PoN ArC5nkQ34ma5zxvUFh3MRjE3+/gxDnUP4pEgSQg5oC1hyM0Rfok809wKgtYZ1tT8 pF7lxxGyHA5WUeseYjVdzma38MAOzOVSfwhhbFpkwr4gIudM83BjRH9fLpq10Y4= =t3tk -----END PGP SIGNATURE----- From mfilpot at gmail.com Sat Feb 25 00:48:02 2012 From: mfilpot at gmail.com (Matthew Fillpot) Date: Fri, 24 Feb 2012 19:48:02 -0500 Subject: [sbopkg-users] New old version of twin is finally up... In-Reply-To: <4F482160.7070200@NorthTech.US> References: <4F482160.7070200@NorthTech.US> Message-ID: On Fri, Feb 24, 2012 at 6:46 PM, Bradley D. Thornton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > Hey I've been really advocating the use of Twin for some time now. It's > better, IMO, than VWM, and VWM is, IMO, better than Twin - it just > depends on which feature set I want to use at the moment I guess. > > Anyway, for over a year now, version 0.6.2 has been available, but it > was at Max's old University site and not sourceforge. I gave him a nudge > after sending the SBo maintainer an email pointing to the newest version > but never heard anything back. Mathhew might have had a lot on his plate > at the time. > > That was fine until one day the original home site for Twin was taken > offline and the new version wasn't up at sourceforge (0.6.1 was the > latest there), so I went to task and Max just uploaded the 0.6.2 version. > > If anyone is so inclined, I've maintained the x86_64 version of the > packages, 0.6.2 being at: > gopher:// > gopher.northtech.us/9/software/packages/twin-0.6.2-x86_64-1_SBo.tgz > but I wouldn't mind at all if Matthew wanted me to take over the > SlackBuild for Twin, considering it's been such a pet project for me > over the past few years anyway - hint hint :) > > I truly believe this is a VERY underutilized tool. > > Anyway, I've BCC'd him on this, seeing how he's the maintainer, and > whichever way he would like to go on this would be great for the > community I'm sure. > > Apologies for being somewhat off-topic if anyone found this post > bothersome. > > Kindest regards, > > > - -- > Bradley D. Thornton > Manager Network Services > NorthTech Computer > TEL: +1.310.388.9469 (US) > TEL: +44.203.318.2755 (UK) > TEL: +41.43.508.05.10 (CH) > http://NorthTech.US > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Find this cert at x-hkp://pool.sks-keyservers.net > > iQEcBAEBAwAGBQJPSCFfAAoJEE1wgkIhr9j3wkIH/RrLkB/Tu7RQRWRkuhYIhTIy > ntMf+bB3KZ2Hh5rkB3GdkXSnlrZwS4dkI2Osy63Dh6F8r+UaxMw3nRzYbhXOCdH/ > YjefM9ztY7FQe9fW0QQot0desindNPAZU9gXWk2KxQyMPnw0CekcyH79+RUu+7L5 > 6jA6ubBdKyBZzH9Pog/vjBAUZlB9Gs4346syEkptq/SpFFedKpwiaXxOrkIoJf++ > J76GBQ6x+cpgobqI167C+YVXifKu4fKdgQs3V8ptxquagM5gkQ1wopFdIyJZ+f+s > fs5k9aK/RVkQZTtB2XLqKojq+7hT4G9JQO32JJtTh8hjm09Y4ZT9VlC67xSqUvw= > =wEKX > -----END PGP SIGNATURE----- > Bradley, Thank you for including me on this e-mail. It looks like your previous attempt to contact me did not make it. I have replaced my prior use of Twin with screen recently, so at this time it would be best for an active user to be the maintainer. With that being said, I will hand off maintenance of Twin to you and I will send a message to the slackbuilds.org mailing list notifying the admins of the change of ownership. -- -Thank You, -Matthew Fillpot -------------- next part -------------- An HTML attachment was scrubbed... URL: