The real problem is that info never caught on in the larger world. Extra packages are impossible in Arch, the maintainers would die from overload. The rukus is really about a handfull of big apps which require oversize docs. If I need info for a Gnu thing, I can grab it off the web and install it myself, just as I do with apps which are not in Arch.
--- James Rayner <[EMAIL PROTECTED]> wrote: > > I agree here too. > > --Not every computer has 24/7 internet > connectivity. > > --Some people really like emacs > > --X is not running on some servers, and reading > docs through lynx/links > > is not as convenient as info. > > > > As for the small package size, if it is that > important we could create > > seperate packages with info documentation. What do > you think? > > > > Well I tried to work out a happy middle ground, but > it went unanswered. > > Most packages that include an info also include a > basic man that works fine. > > For the handfull of packages that ONLY provide an > info, why dont we > use info2man which I put in the AUR earlier to > convert it at the > makepkg? > > Then we get no info pages, people get their man > pages, and everyone is happy. > > James Rayner > > -- > iphitus - archck maintainer > Home:iphitus.loudas.com Blog: iphitus.blogspot.com > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
