headers
Tobias Paepke | 2 Dec 2010 09:42

new question/answer platform

hi fellows,

I'm playing around with a new Question and Answer Platform as _addition_
to the mailinglist. Its inspired by stackoverflow but dedicated to
thinstation.
Well why do I do that? Why would it be a successor.
In my opinion it will solve some issues a mailing list has by design:
 * you can rate answers
 * you don't have to subscribe, but you can for example via rss
 * you can link to already answered questions
 * it has a search engine which suits better that gmane or google on
mailing list archives

I've migrated the FAQ+ of the thinstation.org wiki to test how it feels
and wanted to know from you if there is any space for it in the
thinstation community.

You find it here: http://www.t9n.org

looking forward for your impressions.

greets

tobias

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Eriksen | 20 Dec 2010 15:23
Picon

Suggestion for asystem update package

In most distros you can make updates using tools like apt-get or yum
or whatever. I'd love to have a similar functionality in TS so we can
make trivial updates and bug fixes without having to wait for a new
release.

Trevor has introduced the --update option to "build", but so far it
only is used for updating the IDS files. I think the potential is much
greater.

I suggest a "tsupdate" package. It's a rather banale script looking like this:

packages/tsupdate/build/update:
***
#!/bin/sh
SRC_URL=http://thinstation.org/download/tmp
DELTA_FILE=ts-2.2.2f_update.tar.gz
TSUPDATE=./packages/tsupdate
BACKUP=$TSUPDATE/backup
TODAY=`date +%F`

cd $TSUPDATE
if ! wget -N $SRC_URL/$DELTA_FILE 2>&1 | grep -q "saved"; then
  echo "No new updates for Thinstation are available"
  exit 0
else
  echo "Performing update of Thinstation. Modified files are backed up
in $BACKUP/$TODAY"
  cd ../..

  if [ ! -e $BACKUP/$TODAY ] ; then
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jason Meers | 20 Dec 2010 15:43
Picon

Re: Suggestion for asystem update package

On 20 December 2010 14:23, Mike Eriksen
<thinstation.mike@...> wrote:
> In most distros you can make updates using tools like apt-get or yum
> or whatever. I'd love to have a similar functionality in TS so we can
> make trivial updates and bug fixes without having to wait for a new
> release.
>
> Trevor has introduced the --update option to "build", but so far it
> only is used for updating the IDS files. I think the potential is much
> greater.
>
> I suggest a "tsupdate" package. It's a rather banale script looking like this:
>

Yes I like it.

If it didn't complicate things too much it would be nice to have
channels in addition to "stable" so a new version of rdesktopsvn,
freerdpsvn or xorgsvn could be used if someone SPECIFICALLY requested
it on the command line.

It is not uncommon on other FLOSS projects for individual developers
to have their own testing branches (as new features are being made
stable).

Best regards,

Jason_Meers

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 2 comments |
headers
Tobias Paepke | 20 Dec 2010 19:41

Re: Suggestion for asystem update package

Mike,

great suggestion!

Am 20.12.10 15:23, schrieb Mike Eriksen:
> In most distros you can make updates using tools like apt-get or yum
> or whatever. I'd love to have a similar functionality in TS so we can
> make trivial updates and bug fixes without having to wait for a new
> release.
>
I have to mention: That is covered by thinstation3 with the ipkg
packaging system.

> Trevor has introduced the --update option to "build", but so far it
> only is used for updating the IDS files. I think the potential is much
> greater.
>
Yes, youre right: it has potential. A quite pragmatic approach. like it.
its important to keep easily up2date. We seen the problems we had with
2.2.2e/f.
How would you manage the delta.tar.gz's ? different delta's for every
minor change (incremental changes) or replacing the delta.tar.gz
(differential)?

> It is invoked by "build --update". It looks for a delta file to the
> current version. In the current example thinstation.org is the server,
> but that's only for testing. If accepted SF will be the the host. The
> delta file is only downloaded if it's newer that the local version
> already installed. If a new delta file is downloaded, it is untar'ed
> after the old files are backed up first so you can roll back the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tobias Paepke | 20 Dec 2010 19:46

Re: Suggestion for asystem update package

Am 20.12.10 15:43, schrieb Jason Meers:
> On 20 December 2010 14:23, Mike Eriksen
<thinstation.mike@...> wrote:
>> In most distros you can make updates using tools like apt-get or yum
>> or whatever. I'd love to have a similar functionality in TS so we can
>> make trivial updates and bug fixes without having to wait for a new
>> release.
>>
>> Trevor has introduced the --update option to "build", but so far it
>> only is used for updating the IDS files. I think the potential is much
>> greater.
>>
>> I suggest a "tsupdate" package. It's a rather banale script looking like this:
>>
> Yes I like it.
>
> If it didn't complicate things too much it would be nice to have
> channels in addition to "stable" so a new version of rdesktopsvn,
> freerdpsvn or xorgsvn could be used if someone SPECIFICALLY requested
> it on the command line.
>
-1 cause sometimes you want both in a project. even to play around. ok,
you could double youre build-env.
> It is not uncommon on other FLOSS projects for individual developers
> to have their own testing branches (as new features are being made
> stable).
+1 sounds like a vcs. as i mentioned in my first post to this thread.
would be good to have a testing branch where experienced users can test
their stuff before making a release.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Eriksen | 20 Dec 2010 20:19
Picon

Re: Suggestion for asystem update package

On Mon, Dec 20, 2010 at 3:43 PM, Jason Meers
<jason.meers.energi@...> wrote:
> On 20 December 2010 14:23, Mike Eriksen
<thinstation.mike@...> wrote:
>> In most distros you can make updates using tools like apt-get or yum
>> or whatever. I'd love to have a similar functionality in TS so we can
>> make trivial updates and bug fixes without having to wait for a new
>> release.
>>
>> Trevor has introduced the --update option to "build", but so far it
>> only is used for updating the IDS files. I think the potential is much
>> greater.
>>
>> I suggest a "tsupdate" package. It's a rather banale script looking like this:
>>
>
> Yes I like it.
>
> If it didn't complicate things too much it would be nice to have
> channels in addition to "stable" so a new version of rdesktopsvn,
> freerdpsvn or xorgsvn could be used if someone SPECIFICALLY requested
> it on the command line.
>
> It is not uncommon on other FLOSS projects for individual developers
> to have their own testing branches (as new features are being made
> stable).

That's clearly doable as build already accepts options with parameters
(like --buldtime <file>).
However I have a hard time to see where all these developer versions
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Eriksen | 20 Dec 2010 20:43
Picon

Re: Suggestion for asystem update package

On Mon, Dec 20, 2010 at 7:41 PM, Tobias Paepke
<tobias.paepke@...> wrote:
> Mike,
>
> great suggestion!

[CUT]

>> Trevor has introduced the --update option to "build", but so far it
>> only is used for updating the IDS files. I think the potential is much
>> greater.
>>
> Yes, youre right: it has potential. A quite pragmatic approach. like it.
> its important to keep easily up2date. We seen the problems we had with
> 2.2.2e/f.

Exactly - and the same with 2.2.2c/d.

> How would you manage the delta.tar.gz's ? different delta's for every
> minor change (incremental changes) or replacing the delta.tar.gz
> (differential)?

I'm a minimalist guy, so I imagine a single accumulative delta patch
that can be applied no matter of your current patch level. This means
you can patch up no matter what state your TS version is at - within
the same TS major version. I'm not talking about upgrading 2.2.2 to
2.3, only keeping 2.2.2 a jour. People using rolling releases like
e.g. Gentoo knows how dangerous it is to try to upgrade several
revisions without the intermediate updates. And it is simpler to
manage. The number of updates to TS isn't *that* big that the file
(Continue reading)

Permalink | Reply | 0 comments |

Gmane