Re: installing pine
Quoting Dwight Johnson ([EMAIL PROTECTED]): My condolences. I didn't realize you work at Stonehenge. :-) Yep! BTW, from the Pine Info Center: pine-bin.sun56 . . . . . . . . . Dec 5 16:53 9559k which is 25% of my quota, whereas: 359784 Nov 11 1999 bin/mutt But then I think I would be at great risk of missing high priority personal mail unless it were filtered into its own folder. Definitely worthwhile. Procmail was another program which, until last year, I had to have in my own disk space, though it's now provided. In fact, in that case, I think I would want a cron job to check the personal mail folder and command my computer to emit a beep at intervals to alert me that I have personal mail. There are several biff-type programs available to do just this. But do check that they correctly juggle the modification/access times so that mutt also knows that new mail has arrived. (Particularly if over NFS, apparently.) Search for biff in the Packages file. Submit to your hearts content. These things are a matter of opinion, religion, whatever... I see. Your opinions are a matter of fact, but mine are merely religion. When I post help, I might post opinions with them, particularly when solicited, as here. ^^^ Where does it say they're facts? I am just saying that there's no point in us both writing things like Pine's help and configuration systems are vastly superior to mutt in reply to each other - that's what I meant by a religious discussion. I didn't mean that my views aren't just as much religion or prejudice as yours. BTW I thought power users were users who'd learnt everything and want tools that do just what they want them to do and don't get in their way. So that's the way I used it in my postings. Sorry if you meant something different. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: installing pine
On Tue, Dec 19, 2000 at 03:12:08PM -0800, Adam Shand wrote: You can search the archives to find a link to the deb. There are licensing issues with pine so Debian doesn't include it but there are people who have built the debs. I just snagged the latest stable release (source) from the pine web site. I had to install a library or two but it was no big deal. Compiled just fine. You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. pine, pico and pilot deb's are included in woody. you'll notice that the version numbers have an 'L' at the end of them. that signifies (i believe) that they are not an unmodified binary and allows debian to distribute the pine binaries that they want to and still comply with the license. Actually is just the opposite. The pine license has always allows redistribution of unmodified binaries. The 'L' version number suffix is not needed. However, because of Debian's file system standards we needed to make changes to Pine. Adding the 'L' suffix to the version number indicates that it is a modified binary (I believe 'L' is for Locally modified or something). I'm not sure if the 'L' license clause is something new or if nobody bothered to read the whole license in the past before labelling it as unsuitable for inclusion. Also, the main mirror for the unofficial Pine packages is http://members.mint.net/frodo/pine/ though that may move soon (I'm the person who maintains it). noah -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html pgpJsOZWf300J.pgp Description: PGP signature
Re: installing pine
On Thu, 21 Dec 2000, Noah L. Meyerhans wrote: On Tue, Dec 19, 2000 at 03:12:08PM -0800, Adam Shand wrote: pine, pico and pilot deb's are included in woody. you'll notice that the version numbers have an 'L' at the end of them. that signifies (i believe) that they are not an unmodified binary and allows debian to distribute the pine binaries that they want to and still comply with the license. Actually is just the opposite. The pine license has always allows redistribution of unmodified binaries. The 'L' version number suffix is not needed. However, because of Debian's file system standards we needed to make changes to Pine. Adding the 'L' suffix to the version number indicates that it is a modified binary (I believe 'L' is for Locally modified or something). I'm not sure if the 'L' license clause is something new or if nobody bothered to read the whole license in the past before labelling it as unsuitable for inclusion. I delved into this about the time Pine 4.0 was released... Debian believes it would need permission from the Pine Development Team to redistribute modified binaries, getting permission means that Debian has rights that others do not - which makes it non-free. later, Bruce
Re: installing pine
On Thu, 21 Dec 2000, Bruce Sass wrote: On Thu, 21 Dec 2000, Noah L. Meyerhans wrote: On Tue, Dec 19, 2000 at 03:12:08PM -0800, Adam Shand wrote: pine, pico and pilot deb's are included in woody. you'll notice that the version numbers have an 'L' at the end of them. that signifies (i believe) that they are not an unmodified binary and allows debian to distribute the pine binaries that they want to and still comply with the license. Actually is just the opposite. The pine license has always allows redistribution of unmodified binaries. The 'L' version number suffix is not needed. However, because of Debian's file system standards we needed to make changes to Pine. Adding the 'L' suffix to the version number indicates that it is a modified binary (I believe 'L' is for Locally modified or something). I'm not sure if the 'L' license clause is something new or if nobody bothered to read the whole license in the past before labelling it as unsuitable for inclusion. I delved into this about the time Pine 4.0 was released... Debian believes it would need permission from the Pine Development Team to redistribute modified binaries, getting permission means that Debian has rights that others do not - which makes it non-free. Real freedom includes freedom to fork the code. Unless the Pine license allows this, it's not really free. Dwight
Re: installing pine
Quoting Dwight Johnson ([EMAIL PROTECTED]): These issues concern people who are _not_ beginners. Time is money and taking a lot of time to configure an application is wasteful, when an equal result can be achieved in much less time with Pine. As I said, if you're used to pine, just use the pine bindings, which someone went to the trouble of writing. If you need the exact location, it's /usr/share/doc/examples/Pine.rc . Some years back, storage cost was an issue. But these days, when you can buy a 5Gb drive for $130, the expense of storing Pine is only $0.02. If Pine saved only a single $100 consulting hour in configuration time, the tradeoff would already be gigantic in Pine's favor. The advantage offered by mutt's smaller footprint is nill on any platform larger than a PDA or cellphone. Kindly desist from offering this sort of advice. I am not party to institutional decisions. Oh, and read my signature. On the contrary, the power user does want these aids. The power user wants to make efficient use of his time by being able to quickly access help to execute commands that perhaps he uses only occasionally, like printing an e-mail or finding a particular e-mail by searching for a keyword, without having to search through a nearly endless alphabetical list of commands or waste brain synapses memorizing something he might do only once a week or less. It sounds as if you haven't noticed that / will search and highlight in the help screen as well as elsewhere. There is, in fact, an option in Pine to not display these lines of command prompts. However, in 4-1/2 years of using Pine, I have not yet begun to find these help prompts obtrusive. Well, that surprises me. Only in one respect, that I can see based on my brief exposure, is mutt better -- mutt is a better _threaded_ mail reader. It looks like a lot of effort has been put into mutt's threading features. People who want a threaded mail reader may well prefer mutt. Since I want to process my mail _strictly_ in arrival order, threaded is not a feature I would ever use. It beats me how you can deal with high volume lists (like this one) without threading. Pine's help and configuration systems are vastly superior to mutt -- making Pine much easier to learn and use on a daily basis -- I submit that these features are highly significant for 'power users' who value their time. Submit to your hearts content. These things are a matter of opinion, religion, whatever... When I post help, I might post opinions with them, particularly when solicited, as here. But I'm not interested in discussing religious issues nor indulging in a flame war. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: installing pine
On Tue, Dec 19, 2000 at 12:42:19PM -0800, Dwight Johnson wrote: Only in one respect, that I can see based on my brief exposure, is mutt better -- mutt is a better _threaded_ mail reader. It looks like a lot of effort has been put into mutt's threading features. People who want a threaded mail reader may well prefer mutt. Since I want to process my mail _strictly_ in arrival order, threaded is not a feature I would ever use. I have used pine for a few years and switched to mutt because a bug in 3.96, 4.10 and 4.20 concerning html-attachments. I see the bug is no longer there in 4.31. With Pine I just changed the sort order to the subject-line when I read mailing list and that worked well. Mutt's advantage is that I can delete a whole thread with one keystroke. An advantage of pine which I do not find in mutt is that I could record email addresses from anywhere in the message into the address book. With mutt I can create an alias from the sender's address and have to put other addresses manually in my address book. That is a bit of a nuisance. To keep pine's address book up to date is easier and less prone to errors than mutt's aliases because you can do it from a menu and pine handles all the syntax issues. When forwarding a message using pine, the attachments are included. That is not the case with mutt. Maybe it is something that can be configured. To fine tune mutt takes a lot of time. Something I enjoy about mutt which pine do not provide is the ability to search the contents of all the messages in a mailbox for a string. Another feature of mutt which I could not figure out with pine is the ability to check different mailboxes for new mail. After using mutt for about a year now I enjoy it, but still miss some of pine's abilities. Johann -- J.H. Spies - Tel. 082 782 0336 / 023 55 11 568 And she shall bring forth a son, and thou shall call his name JESUS; for he shall save his people from their sins.Matthew 1:21
Re: installing pine
On Wed, 20 Dec 2000, David Wright wrote: Quoting Dwight Johnson ([EMAIL PROTECTED]): These issues concern people who are _not_ beginners. Time is money and taking a lot of time to configure an application is wasteful, when an equal result can be achieved in much less time with Pine. As I said, if you're used to pine, just use the pine bindings, which someone went to the trouble of writing. If you need the exact location, it's /usr/share/doc/examples/Pine.rc . It was the great help features of Pine which are not developed in mutt which I was referring to when I said 'issues'. The bindings are not an issue. Some years back, storage cost was an issue. But these days, when you can buy a 5Gb drive for $130, the expense of storing Pine is only $0.02. If Pine saved only a single $100 consulting hour in configuration time, the tradeoff would already be gigantic in Pine's favor. The advantage offered by mutt's smaller footprint is nill on any platform larger than a PDA or cellphone. Kindly desist from offering this sort of advice. I am not party to institutional decisions. Oh, and read my signature. duck My condolences. I didn't realize you work at Stonehenge. :-) /duck On the contrary, the power user does want these aids. The power user wants to make efficient use of his time by being able to quickly access help to execute commands that perhaps he uses only occasionally, like printing an e-mail or finding a particular e-mail by searching for a keyword, without having to search through a nearly endless alphabetical list of commands or waste brain synapses memorizing something he might do only once a week or less. It sounds as if you haven't noticed that / will search and highlight in the help screen as well as elsewhere. No, I had not noticed that. I have not yet invested the requisite man-day studying the mutt documentation in order to notice that feature. Thanks for bringing it to my attention. Only in one respect, that I can see based on my brief exposure, is mutt better -- mutt is a better _threaded_ mail reader. It looks like a lot of effort has been put into mutt's threading features. People who want a threaded mail reader may well prefer mutt. Since I want to process my mail _strictly_ in arrival order, threaded is not a feature I would ever use. It beats me how you can deal with high volume lists (like this one) without threading. If I am reading e-mail continually during my work throughout the day, what is optimal is vastly different from reading it perhaps only once or twice a day. In the latter case, the advantages of threaded mailreading are much greater. But then I think I would be at great risk of missing high priority personal mail unless it were filtered into its own folder. In fact, in that case, I think I would want a cron job to check the personal mail folder and command my computer to emit a beep at intervals to alert me that I have personal mail. My pattern of work _is_ changing as I no longer have a business I am glued to. But, to answer your question: when reading and answering e-mail was an integral and continual part of my work, it was no problem dealing with high volume lists without threading because I checked messages so often that I dispatched messages before threads built up. I do acknowledge that the threading and color enhanced features of mutt are really great and way ahead of what Pine has to offer. Pine's help and configuration systems are vastly superior to mutt -- making Pine much easier to learn and use on a daily basis -- I submit that these features are highly significant for 'power users' who value their time. Submit to your hearts content. These things are a matter of opinion, religion, whatever... I see. Your opinions are a matter of fact, but mine are merely religion. When I post help, I might post opinions with them, particularly when solicited, as here. But I'm not interested in discussing religious issues nor indulging in a flame war. Very well then. You get the last word. I am through. I will continue to try to learn and use Mutt as time permits. But when my time is important, I will be forced to continue to use Pine. Dwight
Re: installing pine
On Wed, 20 Dec 2000, Johann Spies wrote: Another feature of mutt which I could not figure out with pine is the ability to check different mailboxes for new mail. If you enable enable-incoming-folders and set incoming-folders to a list of folder names and paths, you can use the TAB key to go to the next mail folder that has new messages. I use this to scan my procmail-sorted mailing list folders, and it works quite nicely (similar to the way GNUS goes to the next folder/group). Brad
Re: installing pine
On Mon, 18 Dec 2000, David Wright wrote: Quoting Dwight Johnson ([EMAIL PROTECTED]): On Sun, 17 Dec 2000, ktb wrote: You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. I have recently been trying mutt and, quite honestly, I have find mutt a lot clunkier than Pine. One example: when you call up Pine for the first time in any home directory, Pine creates a default .pinerc and it is extremely easy to customize Pine from the Pine master menu. In contrast, with mutt, no .muttrc is created automatically on first use and evidently there exists no easy to use configuration program (at least I have been unable to find one) as there is in Pine. These are the sorts of issues that concern beginners who can be helped by having a good /etc/Muttrc file. Power users aren't really concerned. These issues concern people who are _not_ beginners. Time is money and taking a lot of time to configure an application is wasteful, when an equal result can be achieved in much less time with Pine. As my institutional copy of mutt resides in my own disk space (they don't support it), I would be disappointed at being quota'd for all that redundant help. Some years back, storage cost was an issue. But these days, when you can buy a 5Gb drive for $130, the expense of storing Pine is only $0.02. If Pine saved only a single $100 consulting hour in configuration time, the tradeoff would already be gigantic in Pine's favor. The advantage offered by mutt's smaller footprint is nill on any platform larger than a PDA or cellphone. It took me an hour of wading through documentation to figure out how to just get my 'From:' header to display my e-mail address. Apparently, I must do the same for each item of customization I want in mutt. Another example: control and navigation keys are clearly displayed at the bottom of each Pine screen. For the equivalent functionality in mutt, I must press '?' and wade through a gadzillion keys displayed over multiple screens. ... for the power user, there's no desire for real estate to be wasted on stuff like that. On the contrary, the power user does want these aids. The power user wants to make efficient use of his time by being able to quickly access help to execute commands that perhaps he uses only occasionally, like printing an e-mail or finding a particular e-mail by searching for a keyword, without having to search through a nearly endless alphabetical list of commands or waste brain synapses memorizing something he might do only once a week or less. There are very few different commands you actually need just to read day-to-day emails, and the keystrokes needed can be (and are by default?) displayed in one line. This is true, but there are many less frequently used commands that will not be committed to memory -- and Pine makes these much more accessible for quick use than mutt. There is, in fact, an option in Pine to not display these lines of command prompts. However, in 4-1/2 years of using Pine, I have not yet begun to find these help prompts obtrusive. So I am very surprised to hear you say that you think Pine is clunkier than mutt. I would welcome learning in what ways. Configurability, customisability, whatever, of keystrokes and status information for each type of screen, navigation, colours, headers, editor, etc. What I seriously doubt that -- getting into the specifics -- mutt is superior to Pine in configurability and customisability. Only in one respect, that I can see based on my brief exposure, is mutt better -- mutt is a better _threaded_ mail reader. It looks like a lot of effort has been put into mutt's threading features. People who want a threaded mail reader may well prefer mutt. Since I want to process my mail _strictly_ in arrival order, threaded is not a feature I would ever use. I am willing to give mutt a try based on its purer free software license. But I have used Pine to process in excess of 300 mails a day, including a high volume of personal mail, for long stretches over 4-1/2 years. Pine is extremely well designed to process and archive a high volume of mail quickly. My mail archive is currently 14Mb in 489 folders. If Pine were a lightweight program, I would have noticed it by now and changed to something else. Pine's help and configuration systems are vastly superior to mutt -- making Pine much easier to learn and use on a daily basis -- I submit that these features are highly significant for 'power users' who value their time. The mutt developers have much to learn from Pine (and I'm sure have already learned much). It is too bad the Pine license is flawed. Fortunately, this is only slightly and should not inhibit our use of Pine while we continue to support the development of completely free mailreaders like mutt. Dwight
Re: installing pine
You can search the archives to find a link to the deb. There are licensing issues with pine so Debian doesn't include it but there are people who have built the debs. I just snagged the latest stable release (source) from the pine web site. I had to install a library or two but it was no big deal. Compiled just fine. You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. pine, pico and pilot deb's are included in woody. you'll notice that the version numbers have an 'L' at the end of them. that signifies (i believe) that they are not an unmodified binary and allows debian to distribute the pine binaries that they want to and still comply with the license. heyzeus(larry)$ apt-cache search pine pico - Easy-to-use text editor found in Pine. pine - An e-mail reader with MIME and IMAP support. pilot - simple file system browser in the style of the Pine Composer. pine-docs - Getting started with email using Pine heyzeus(larry)$ apt-cache show pine | grep Version Version: 4.21L-0.3 adam.
Re: installing pine
Quoting Dwight Johnson ([EMAIL PROTECTED]): On Sun, 17 Dec 2000, ktb wrote: You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. I have recently been trying mutt and, quite honestly, I have find mutt a lot clunkier than Pine. One example: when you call up Pine for the first time in any home directory, Pine creates a default .pinerc and it is extremely easy to customize Pine from the Pine master menu. In contrast, with mutt, no .muttrc is created automatically on first use and evidently there exists no easy to use configuration program (at least I have been unable to find one) as there is in Pine. These are the sorts of issues that concern beginners who can be helped by having a good /etc/Muttrc file. Power users aren't really concerned. As my institutional copy of mutt resides in my own disk space (they don't support it), I would be disappointed at being quota'd for all that redundant help. It took me an hour of wading through documentation to figure out how to just get my 'From:' header to display my e-mail address. Apparently, I must do the same for each item of customization I want in mutt. Another example: control and navigation keys are clearly displayed at the bottom of each Pine screen. For the equivalent functionality in mutt, I must press '?' and wade through a gadzillion keys displayed over multiple screens. There's a set of key bindings in the deb for people used to pine. Again, for the power user, there's no desire for real estate to be wasted on stuff like that. I would gladly convert to mutt from Pine just to get a more pure open source license. But, in my opinion, the clunkiness of mutt makes such a conversion quite formidable when I must still read my e-mail each day. There are very few different commands you actually need just to read day-to-day emails, and the keystrokes needed can be (and are by default?) displayed in one line. So I am very surprised to hear you say that you think Pine is clunkier than mutt. I would welcome learning in what ways. Configurability, customisability, whatever, of keystrokes and status information for each type of screen, navigation, colours, headers, editor, etc. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
installing pine
Hi all... curious.. I'm trying to install pine via apt-get but it tells me package found but can't be installed.. I don't have the exact error message (it was late. ;-). has anyone else been able to install pine? thanks xucaen __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Re: installing pine
On Sun, Dec 17, 2000 at 09:55:42AM -0800, Xucaen wrote: Hi all... curious.. I'm trying to install pine via apt-get but it tells me package found but can't be installed.. I don't have the exact error message (it was late. ;-). has anyone else been able to install pine? You can search the archives to find a link to the deb. There are licensing issues with pine so Debian doesn't include it but there are people who have built the debs. I just snagged the latest stable release (source) from the pine web site. I had to install a library or two but it was no big deal. Compiled just fine. You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. hth, kent -- In order to make an apple pie from scratch, you must first create the universe. - Carl Sagan
Re: installing pine
Xucaen wrote: Hi all... curious.. I'm trying to install pine via apt-get but it tells me package found but can't be installed.. I don't have the exact error message (it was late. ;-). has anyone else been able to install pine? yes i downloaded the 3rd party pine packages a while back and have a mirror if you want to get them, http://portal.aphroland.org/debian/packages/ i don't remember the original site ..and my site is not apt'able nate -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Re: installing pine
On Sun, 17 Dec 2000, ktb wrote: You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. I have recently been trying mutt and, quite honestly, I have find mutt a lot clunkier than Pine. One example: when you call up Pine for the first time in any home directory, Pine creates a default .pinerc and it is extremely easy to customize Pine from the Pine master menu. In contrast, with mutt, no .muttrc is created automatically on first use and evidently there exists no easy to use configuration program (at least I have been unable to find one) as there is in Pine. It took me an hour of wading through documentation to figure out how to just get my 'From:' header to display my e-mail address. Apparently, I must do the same for each item of customization I want in mutt. Another example: control and navigation keys are clearly displayed at the bottom of each Pine screen. For the equivalent functionality in mutt, I must press '?' and wade through a gadzillion keys displayed over multiple screens. I would gladly convert to mutt from Pine just to get a more pure open source license. But, in my opinion, the clunkiness of mutt makes such a conversion quite formidable when I must still read my e-mail each day. So I am very surprised to hear you say that you think Pine is clunkier than mutt. I would welcome learning in what ways. Dwight
Re: installing pine
Dwight Johnson [EMAIL PROTECTED] said: So I am very surprised to hear you say that you think Pine is clunkier than mutt. I would welcome learning in what ways. I cut my teeth on Pine and Pico. About a year ago, I started playing with mutt, and was quickly frustrated by the appearant complexity and non-intuitive interface, so I gave up. Six months later, I finally learned how to use vi instead of pico for everything, and realized that intuitiveness is a matter of perspective; you just have to be in the right frame of mind. Now it's hard for me to use pico (nano) for anything useful, let alone editing complex files. Once you become accustomed to mutt, the keybindings, making your own filters, et cetera, pine will become like a pair of training wheels; crucial at one time, but impossible to use now. Trust me, it's worth using for a week. I still don't use mutt because of the high volume of mail I receive and process every day at work. On the other hand, for my personal accounts, mutt is the only client I'll use willingly. There are also a number of tools on the interet to make configuring and extending mutt easier; check Freshmeat.net. -- -=|JP|=- Jon Pennington| Atipa Linux Solutions [EMAIL PROTECTED] | http://www.atipa.com Kansas City, MO, USA | 816-595-3000 x1550
Re: installing pine
On Sun, Dec 17, 2000 at 01:12:27PM -0800, Dwight Johnson wrote: On Sun, 17 Dec 2000, ktb wrote: You might want to try mutt. I like it a lot better. It took some configuring but it isn't as clunky as pine. I have recently been trying mutt and, quite honestly, I have find mutt a lot clunkier than Pine. One example: when you call up Pine for the first time in any home directory, Pine creates a default .pinerc and it is extremely easy to customize Pine from the Pine master menu. In contrast, with mutt, no .muttrc is created automatically on first use and evidently there exists no easy to use configuration program (at least I have been unable to find one) as there is in Pine. It took me an hour of wading through documentation to figure out how to just get my 'From:' header to display my e-mail address. Apparently, I must do the same for each item of customization I want in mutt. Another example: control and navigation keys are clearly displayed at the bottom of each Pine screen. For the equivalent functionality in mutt, I must press '?' and wade through a gadzillion keys displayed over multiple screens. I would gladly convert to mutt from Pine just to get a more pure open source license. But, in my opinion, the clunkiness of mutt makes such a conversion quite formidable when I must still read my e-mail each day. So I am very surprised to hear you say that you think Pine is clunkier than mutt. I would welcome learning in what ways. As I said above it takes some configuring. It isn't easy to learn. Pine is. As with most unix programs and the os itself some have easy installation and configuration and others don't. When I said clunky I was referring to usage not installation and configuration. It took me a day to get mutt set up how I liked. It took a couple more before I became comfortable with using the program itself. If your serious about wanting to use mutt just set the directory mutt uses to pick up mail as a symbolic link to pine's mail directory. In other words create the link Mail (mutt) pointing to mail (pine) in your home directory. Doing this allows you to use both mailers with the same mail. That way you can ease into mutt and still use pine until you become comfortable with it. kent -- In order to make an apple pie from scratch, you must first create the universe. - Carl Sagan
Re: installing pine
On Sun, 17 Dec 2000, Xucaen wrote: Hi all... curious.. I'm trying to install pine via apt-get but it tells me package found but can't be installed.. I don't have the exact error message (it was late. ;-). has anyone else been able to install pine? Yes. Install pine4-diffs and everything that it recommends, then follow the instructions from the README in /usr/src/pine4. Pine is distributed as source only due to license restrictions. Type apt-cache show pine4-diffs to see what other packages it recommends. Brad
Re: Need help installing Pine
On Wed, 30 Jun 1999, Larry Huffman wrote: steps taken: dpkg-source -x pine_v.dsc cd pine debian/rules binary (as root) error message received: test -f pine/pine.c -a -f debian/rules debian/rules binaryPine make[1]: Entering directory `/usr/src/pine/pine-v' test -f pine/pine.c -a -f debian/rules test root = `whoami` rm -rf debian/tmp install -d debian/tmp/DEBIAN debian/tmp/usr/lib/menu cd debian/tmp install -d usr/bin usr/man/man1 usr/doc/pine cd debian install -m 755 postinst postrm tmp/DEBIAN cd debian install -m 644 menu.pine tmp/usr/lib/menu/pine install bin/pine debian/tmp/usr/bin install: bin/pine: No such file or directory make[1]: *** [binaryPine] Error 1 This means the pine binary could not be created, for some unspecified reason. My guess is that maybe you don't have libncurses4-dev installed, but it's difficult to say without more data (if you have the complete logs, it would help). In case of difficulty, try to do it in two steps: debian/rules build as a normal user [ coffee here ] debian/rules binary as root. Hope this helps.
Need help installing Pine
After two years of using Red Hat, I've turned my attention to Debian (Slink), and am learning my way around the packaging system, apt, and dpkg. I'm now trying to install Pine. (This message, BTW, is coming from my shell account at my ISP, hence it being from Pine.) I've tried to install both of the following sets of source packages, using the same steps (listed below), receiving the same error message (also provided below): sources: pine_4.10-0.dsc pine_4.10-0.diff.gz pine_4.10.orig.tar.gz pine_3.96M-2.dsc pine_3.96M-2.diff.gz pine_3.96M.orig.tar.gz steps taken: dpkg-source -x pine_v.dsc cd pine debian/rules binary (as root) error message received: test -f pine/pine.c -a -f debian/rules debian/rules binaryPine make[1]: Entering directory `/usr/src/pine/pine-v' test -f pine/pine.c -a -f debian/rules test root = `whoami` rm -rf debian/tmp install -d debian/tmp/DEBIAN debian/tmp/usr/lib/menu cd debian/tmp install -d usr/bin usr/man/man1 usr/doc/pine cd debian install -m 755 postinst postrm tmp/DEBIAN cd debian install -m 644 menu.pine tmp/usr/lib/menu/pine install bin/pine debian/tmp/usr/bin install: bin/pine: No such file or directory make[1]: *** [binaryPine] Error 1 make[1]: Leaving directory `/usr/src/pine/pine-3.96M' make: *** [binary-arch] Error 2 I searched the archives for this list but couldn't find anything; I thought I saw something posted about this earlier this month. Thanks in advance for any help. Debian's great thus far. -- Larry
Help a newbie installing pine
I'm not sure if I missed a package when downloading hamm or something, but pine was not included, so I downloaded the newest version available from washington university. However, whenever I try to build it using the linux option, I get an error ld cannot open -ltermcap: no such file or directory. Please help if you know what I should do about this error. Thanks.
Re: Help a newbie installing pine
The pine license doesn't permit distribution of modified binaries, so you should get the pine396-src and pine396-diff packages and build the debian package (see /usr/src/pine/README after installing the packages). Also, there's a newer version of pine in /debian/project/experimental on the Debian mirrors. Bob On Sun, 24 Jan 1999, Darknight wrote: I'm not sure if I missed a package when downloading hamm or something, but pine was not included, so I downloaded the newest version available from washington university. However, whenever I try to build it using the linux option, I get an error ld cannot open -ltermcap: no such file or directory. Please help if you know what I should do about this error. Thanks. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Re: Help a newbie installing pine
On Sun, 24 Jan 1999, Darknight wrote: I'm not sure if I missed a package when downloading hamm or something, but pine was not included, so I downloaded the newest version available from washington university. However, whenever I try to build it using the linux option, I get an error ld cannot open -ltermcap: no such file or directory. Please help if you know what I should do about this error. Thanks. Your easiest fix is to look on a debian mirror, in /project/experimental, and download pine.*. These will then build fine. Matthew -- Elen sila lumenn' omentielvo Steward of the Cambridge Tolkien Society Selwyn College Computer Support http://www.geocities.com/Area51/Chamber/8841/ http://www.cam.ac.uk/CambUniv/Societies/tolkien/ http://pick.sel.cam.ac.uk/
Re: Help a newbie installing pine
Darknight [EMAIL PROTECTED] writes: However, whenever I try to build it using the linux option, I get an error ld cannot open -ltermcap: no such file or directory. Do you have ncurses-dev (sp?) installed? AFAIR it installs libtermcap.* as symlinks to libcurses.*. -- Henning Makholm http://www.diku.dk/students/makholm
Installing pine 4.05
Anybody installed this package from project/experimental? I replaced -ltermcap with -lncurses as suggested elsewhere but still I cannot compile the package becuase it is looking for a crypt() function. Any help? I am having a problem with apps that are color intensive (eg netscape) and font intensive (e.g StarOffice). After I run one of these apps I have a problem running other apps (e.g. plan). They come in different reduced colors. Is there anything I can do? /--/ Daniel J. Mashao Electrical Engineering [EMAIL PROTECTED] University of Cape Town http://www.ee.uct.ac.za/~daniel Rondebosch, 7700, S. Africa (w) 27+21+650 2816 (h) 27+21+705 8469 /--/
Re: Installing pine 4.05
On Fri, 2 Oct 1998, Daniel Mashao wrote: Anybody installed this package from project/experimental? I replaced -ltermcap with -lncurses as suggested elsewhere but still I cannot compile the package becuase it is looking for a crypt() function. Once more I have to say: Please, do not modify the source yourself. Use the Debian patches. In doubt, read the README file from the pine396-diffs package in hamm. Thanks.
