Steve Graegert wrote:

On 10/10/05, Basil Chupin wrote:

...

Does anyone know if there is a copy of an RPM version of tvtime 1.0.1 and where I can get such a beast? (The best SuSE has is still the ancient 0.99.5 :-( .)

Don't know where to get it from, but may I ask why you need an RPM? Do you have trouble with the sources? I compiled tvtime a couple of days ago and it works perfectly well (including IR).

I had no problem compiling it but I also have 3 computers and having to compile the darn thing 3x is a pain; it would be so much more efficient if there was a RPM available. Cheers. -- Don't argue with an idiot, people may not see the difference.

Per Qvindesland wrote:

Why don't you just make a rpm out of it by using rpmbuild? do a man rpmbuild which explains the usage also have a look here for an alternative way http://www.novell.com/coolsolutions/feature/11793.html

Regards

On Monday 10 October 2005 09:48, Basil Chupin wrote:

...

Steve Graegert wrote:

...

On 10/10/05, Basil Chupin wrote:

...

Does anyone know if there is a copy of an RPM version of tvtime 1.0.1 and where I can get such a beast? (The best SuSE has is still the ancient 0.99.5 :-( .)

Don't know where to get it from, but may I ask why you need an RPM? Do you have trouble with the sources? I compiled tvtime a couple of days ago and it works perfectly well (including IR).

I had no problem compiling it but I also have 3 computers and having to compile the darn thing 3x is a pain; it would be so much more efficient if there was a RPM available.

Cheers.

Thanks for the suggestion. If it was that easy to make a RPM then why are RPMs made available for download? I've (tried to) read the 'man rpmbuild' and need a manual to make me understand what is in 'man rpmbuild'. Any suggestions where I can find such a manual? Cheers. -- Don't argue with an idiot, people may not see the difference.

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Friday 2005-10-14 at 16:06 +1000, Basil Chupin wrote:

...

Thanks for the suggestion.

If it was that easy to make a RPM then why are RPMs made available for download?

...

:-}

...

I've (tried to) read the 'man rpmbuild' and need a manual to make me understand what is in 'man rpmbuild'.

Yeap.

...

Any suggestions where I can find such a manual?

Use checkinstall instead. Just substitute the "make install" phase by "chekinstall". Ie (in general):

./configure make su checkinstall exit

- -- Cheers, Carlos Robinson

Ah, now that's something which is most informative and useful. And it actually works to boot! Thanks for that. Cheers. -- Don't argue with an idiot, people may not see the difference.

Sid Boyce wrote:

Basil Chupin wrote:

...

Per Qvindesland wrote:

<STUFF DELETED>

...

If it was that easy to make a RPM then why are RPMs made available for download?

I've (tried to) read the 'man rpmbuild' and need a manual to make me understand what is in 'man rpmbuild'.

Any suggestions where I can find such a manual?

Cheers.

Thereby hangs a tale, not all source packages contain the spec files to allow rpmbuild to do its thing, that's why checkinstall is so useful. My approach to the rpmbuild manual is to use what does the job rather than trying to get a complete understanding of all the options the real experts relish, it's my way of working, I've been using vi regularly for the last 23 years, but I only do simple things with it, so many newbies can teach me a thing or two about using it, however, I gets the job done without having to learn obscure things. rpmbuild --rebuild package.src.rpm rpmbuild -ta package.tar.* (if it works, checkinstall if it doesn't) rpmbuild -ba package.spec Regards Sid.

Thanks for this, Sid. I have now entered this into my Notebook of Wisdom and will try it/them out in the near future. I tried using vi not too long ago and couldn't exit the damn thing once I fired it up :-). I had to reboot to get out of it. So I decided to stick with pico which even I can work. Cheers. -- Don't argue with an idiot, people may not see the difference.

Ken, Basil, On Sunday 16 October 2005 04:37, Ken Schneider wrote:

On Sun, 2005-10-16 at 16:46 +1000, Basil Chupin wrote:

...

Sid Boyce wrote:

...

Basil Chupin wrote:

...

Per Qvindesland wrote:

<STUFF DELETED>

Thanks for this, Sid. I have now entered this into my Notebook of Wisdom and will try it/them out in the near future.

I tried using vi not too long ago and couldn't exit the damn thing once I fired it up :-). I had to reboot to get out of it. So I decided to stick with pico which even I can work.

That's far more drastic an action that is ever required in such a situation. There are myriad ways to deal with a hung application (equivalently, one you cannot figure out how to exit!). If you're running in a GUI environment, create a new terminal window (in the same way you created the one in which the program you cannot escape is running). Then use this command to find the process ID of the command: % pidof vi Assuming there's just one such process and hence no ambiguity about which to kill, next issue this command: % kill PID-of-Vi

When using vi the easiest way to exit is with two Z characters after hitting the esc key or you can hit esc and then :q! to quit. It's easy when you know how, not so easy when you don't.

Those two ways out are not equivalent. ZZ is identical to :x which is identical to :wq (all of which will write a modified buffer without asking before quitting). On the other hand, :q! quits without saving a modified buffer and without asking if you want to do that. The simple :q command will quit only if the buffer is not modified. If it is modified, it will complain that there are unsaved changes. No matter how many times you repeat it, :q will not quit with unsaved changes extant. The various quit / exit commands will also remind you if you try to quit without having visited the entire list of files given on the command line, but that warning is not repeated on subsequent attempts to quit (unless another command intervenes). Vi is great, eh?

-- Ken Schneider

Randall Schulz

On Sun, Oct 16, 2005 at 04:46:18PM +1000, Basil Chupin took 59 lines to write: [...]

I tried using vi not too long ago and couldn't exit the damn thing once I fired it up :-). I had to reboot to get out of it. So I decided to stick with pico which even I can work.

To exit vi, press Esc a couple of times, then type, sans quotes, ":q". Kurt -- Serenity through viciousness.