February 2011 - Arch-general - lists.archlinux.org

Re: [arch-general] [arch-dev-public] Vi package
by Loui Chang 11 Feb '11

11 Feb '11

On Wed 09 Feb 2011 11:23 -0500, Stéphane Gaudreault wrote: > Hi, > > I was looking at FS#20778 and was wondering what we should do with it. > > While it is true that the "traditional vi" is buggy and not user > friendly. It does not seems that BusyBox is a good alternative. > > There are options here: > > 1) Statu quo > Pro : > * Support for multi-byte character encodings like UTF-8 > * Small size > Cons : > * Did I said that it is buggy ? > * Use of this old software in the installer may give a strange > impression to new users as they are faced with an editor from the > '70 on a distro where everything is up to date. > * Appears to be no longer be updated upstream. > > Opinions? I'd say stick with the status quo. I don't find anything too wrong with the traditional vi. There's the file size and line length limit and those aren't really that bad. The wide terminal issue has been worked around by changing the config header. If you want to do heavy editing other programs are more appropriate in our modern age. Vi is more appropriate for light editing like when doing installation or configuration. Are other bugs that you mention documented somewhere? I'm interested in learning about them. If you can use vim you probably should be able to use vi without too much difficulty. I guess you could argue that having two basic editors (vi and nano) is unnecessary, vi is usually expected to be on a basic system, and nano just bugs me. :D

1 0

Re: [arch-general] [arch-dev-public] Vi package
by Marek Otahal 10 Feb '11

10 Feb '11

On Thursday 10 of February 2011 17:59:26 Pierre Schmitz wrote: > On Thu, 10 Feb 2011 17:52:16 +0100, Jan de Groot wrote: > > On Thu, 2011-02-10 at 17:24 +0200, Ionuț Bîru wrote: > >> we did had vi being a stripped vim package in the past. We got rid of > >> it > >> because upstream vim started to not helping arch users because "it > >> was > >> broken". That impression was given by our users who didn't understand > >> that python and other crap that vim support is in vim package and not > >> in vi. > >> > >> now the same situation is now. Some users don't understand that vi is > >> nvi and what they want is in vim. > > > > I don't think we should go back to a fucked vim package with /etc/virc > > like we had it in the past. We switched from that to nvi, which fucked > > up files if they contained unicode stuff (it would just segfault in the > > middle of a save operation, leaving you with a broken file). > > After that, we decided to go for busybox, which works fairly well as vi, > > is maintained, but doesn't do anything that looks like vim. > > > > IMHO vi is totally useless on most systems. I prefer to uninstall it and > > do ln -s vim /usr/bin/vi instead. Users who complain about vi being too > > limited should do that too. > > I wonder the same. I cannot imagine why anybody would want to use vi. > Personally I would not mind if nano was the only interactive editor in > [core]. But keeping the current busybox vi is also fine. Hello, first, I apologize for off-topic, but i seek help on vim. Reading this thread I decided I want to learn how to get more from vim, so I started with vimtutor. So far I ran into two issues that were incompatible with the vimtutor, *) 7G moves you to line 7, I had to do 7gg instead *) " Lesson 5.3: SELECTING TEXT TO WRITE ** To save part of the file, type v motion :w FILENAME ** 1. Move the cursor to this line. 2. Press v and move the cursor to the fifth item below. Notice that the text is highlighted. 3. Press the : character. At the bottom of the screen :'<,'> will appear. 4. Type w TEST , where TEST is a filename that does not exist yet. Verify that you see :'<,'>w TEST before you press <ENTER>. 5. Vim will write the selected lines to the file TEST. Use :!dir or !ls to see it. Do not remove it yet! We will use it in the next lesson. "...this doesn't work for me, I switch to visual mode, after : the '<,'> doesn't appear though. Can somebody enlighten me, is this behavior -some config in vim -- where and how can I set it? -mistakes in the tutorial (could be updated) -mistakes in vim Many thanks, mark the vimmer :) -- Marek Otahal :o)

2 1

[arch-general] trinity pkgbuild: rewrite to dl svn - Use fixed svn rev or latest?
by David C. Rankin 10 Feb '11

10 Feb '11

Guys, I'm rewriting a set trinity pkgbuilds to download the trinity/<module> code in the pkgbuild instead of using the existing source in the local copy of the complete trinity svn tree. This will also allow the packages to be built in an archroot and get around the empty src problem I was having with makechrootpkg using the code in the existing tree. My PKGBUILD question is can I use the latest svn revision to build from, or do I need to use a fixed svn revision for $pkgver? The examples I've looked at do something like: pkgver=123456 <snip> build() { cd $srcdir msg "Connecting to $_svntrunk SVN server...." if [ -d $_svnmod/.svn ]; then (cd $_svnmod && svn up -r $pkgver) else svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod fi <snip> I want to vary this to use the latest revision instead of a fixed revision: pkgver=123456 <snip> build() { cd ${srcdir} msg "Connecting to SVN server...." if [ -d ${_svn_module}/.svn ]; then (cd ${_svn_module} && svn up) [[ $? -eq 0 ]] || _co_failed=1 else (svn co $_svn_trunk ${_svn_module}) [[ $? -eq 0 ]] || _co_failed=1 fi cd ${_svn_module} pkgver=$(getsvnrev) <snip> Is this OK, or should I avoid using the latest version to prevent potential inconsistencies? Also, if you see anything else that will bite me, let me know. Thanks. -- David C. Rankin, J.D.,P.E.

3 5

Re: [arch-general] [arch-dev-public] Fwd: [arch-dev] [signoff] ppp-2.4.5-2
by Dave Reisner 10 Feb '11

10 Feb '11

On Wed, Feb 09, 2011 at 03:26:29PM -0500, Eric Bélanger wrote: > Forwarding to public ML. > > > ---------- Forwarded message ---------- > From: Stéphane Gaudreault <stephane(a)archlinux.org> > Date: Wed, Feb 9, 2011 at 2:23 PM > Subject: [arch-dev] [signoff] ppp-2.4.5-2 > To: arch-dev(a)archlinux.org > > > * Rebuild of old package > * Tidy up PKGBUILD > * Fix build error with recent kernel > * Fix permissions on libs > > Please signoff both as I do not run this pkg. > Thanks > > Stéphane I recall last time there was a new build of ppp around, it came down to user signoffs. In case it comes down to that again, I can still connect to my VPN, so I'll sign off for x86_64. dave

1 0

[arch-general] xinitrc.d framework
by Yclept Nemo 10 Feb '11

10 Feb '11

I hacked an "xinitrc.d framework". The details are at https://wiki.archlinux.org/index.php/Xinitrc.d_Framework. I'm only one person, so I'd appreciate any comments.

3 2

[arch-general] Package update : hplip 3.11.1
by Rémy Oudompheng 10 Feb '11

10 Feb '11

HPLIP 3.11.1 was released several days ago : it includes support for new printers and scanning support for several printers (e.g. the one I bought last week, HP Deskjet 2050). I thought the package was not very critical so that I could update it directly in [extra]. I can at least print and scan (hp-scan still doesn't work with my printer, but scanimage does). Now you know who you can blame if your printer suddenly stops working at next update. -- Rémy.

1 0

Re: [arch-general] [arch-dev-public] makepkg bug with epoch code
by Ng Oon-Ee 09 Feb '11

09 Feb '11

On Wed, 2011-02-09 at 20:52 +1000, Allan McRae wrote: > On 09/02/11 20:46, Allan McRae wrote: > > Have not had time to look into this, but I get this error with the > > kernel26 PKGBUILD in Arch Linux [core] repo: > > > > umm.. wrong list :P > Allan broke it!

1 0

[arch-general] Crazy devs....
by Ng Oon-Ee 09 Feb '11

09 Feb '11

I saw a pidgin update (2.7.10) and while downloading I thought I'd check the changelog. Go to pidgin.im, and the most recent version is 2.7.9. Its official, Arch Linux devs are faster than upstream! Shout-out to Ionut Biru and indeed to all the devs who make Arch Linux great =)

3 2

[arch-general] Trinity on Arch - I need a mentor
by David C. Rankin 09 Feb '11

09 Feb '11

Guys, My project to develop PKGBUILDs for Trinity on Arch has made good progress, but I have hit a couple of snags where I could really use an experienced mentor who is good with complex package builds on Arch. I have a current status on the wiki: https://wiki.archlinux.org/index.php/Trinity I'll do the heavy lifting, I just need someone to point me in the right direction and bounce ideas off of. Anybody interested in looking over the status and helping move me off high-center? -- David C. Rankin, J.D., P.E.

1 0

[arch-general] makechrootpkg - not using cmake environment from PKGBUILD - help?
by David C. Rankin 09 Feb '11

09 Feb '11

Guys, I am having 2 difficulties building in my archroot environment. I have created the archroot in /home/david/chbld/root. I have managed to build trinity-qt3, trinity-pyqt3 and trinity-tqtinterface in the archroot, but now when I start building packages that rely on the installed package environment, I am encountering errors: (1) The pkgbuilds use exports to set the cmake environment. eg.: export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt this works fine in the virtualbox clean environment, but fails in the mkarchroot. For example, building trinity-arts: [100%] Building CXX object qtmcop/CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o cd /build/src/arts-bld/qtmcop && /usr/bin/c++ -Dqtmcop_shared_EXPORTS -DHAVE_CONFIG_H -march=i686 -mtune=generic -O2 -pipe -fPIC -I/build/src/arts-bld/qtmcop -I/build/src/arts-bld/mcop -o CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o -c /build/src/arts-bld/qtmcop/qiomanager.cc In file included from /build/src/arts-bld/qtmcop/qiomanager.cc:23:0: /build/src/arts-bld/qtmcop/qiomanager.h:33:22: fatal error: tqobject.h: No such file or directory compilation terminated. make[2]: *** [qtmcop/CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o] Error 1 make[2]: Leaving directory `/build/src/arts-bld' make[1]: *** [qtmcop/CMakeFiles/qtmcop-shared.dir/all] Error 2 make[1]: Leaving directory `/build/src/arts-bld' make: *** [all] Error 2 Aborting... tqobject.h is right where it should be in the rw chroot structure: 20:20 providence:~/chbld/tbld/trinity-arts> l ~/chbld/copy/opt/qt/include/tqt/tqobject.h -rw-r--r-- 1 root root 1139 Feb 8 17:49 /home/david/chbld/copy/opt/qt/include/tqt/tqobject.h The PKGBUILD I'm attempting to use is here in full: http://www.3111skyline.com/dl/dt/trinity/arch/svn/dependencies/arts/PKGBUIL… Why is makechrootpkg not respecting the cmake environment variable for CMAKE_INCLUDE_PATH? (2) The archroot isn't handling dependencies from the custom local repository requiring that packages be manually installed with makechrootpkg -r <chrootdir> -I <package> I'm a bit bewildered here. (happens) I have created the chroot repo in ~/chbld/root/chrepo and used repo-add to create the index: 20:49 providence:~/chbld> ls -1 ~/chbld/root/chrepo/ chrepo.db chrepo.db.tar.gz chrepo.db.tar.gz.old trinity-pyqt3-3.18.1-9-i686.pkg.tar.xz trinity-qt3-3.3.8-20-i686.pkg.tar.xz trinity-tqtinterface-9999-1-i686.pkg.tar.xz I've added the entry to ~/chbld/root/etc/pacman.conf: <snip> [core] Include = /etc/pacman.d/mirrorlist # mkarchroot repo [chrepo] Server = file:///chrepo [extra] Include = /etc/pacman.d/mirrorlist [community] Include = /etc/pacman.d/mirrorlist <snip> The repository index is read during the makechrootpkg call is for all things -- looks fine: 18:51 providence:~/chbld/root/home> sudo mkarchroot -u /home/david/chbld/root/ :: Synchronizing package databases... core is up to date chrepo 1.0K 8.7M/s 00:00:00 [#####################################] 100% extra is up to date community 427.8K 586.7K/s 00:00:01 [#####################################] 100% :: Starting full system upgrade... there is nothing to do But when a PKGBUILD lists a package in chrepo as a dependency, the build fails with: 17:23 providence:~/chbld/tbld/trinity-tqtinterface> sudo makechrootpkg -r /home/david/chbld ==> Making package: trinity 9999-1 (Tue Feb 8 23:23:28 UTC 2011) ==> Checking Runtime Dependencies... ==> Installing missing dependencies... error: 'trinity-qt3': could not find or read package ==> ERROR: 'pacman' failed to install missing dependencies. Build failed, check /home/david/chbld/copy/build Any reason makechroot is not installing dependencies from the local chrepo stand out? Thanks for any help you can provide on either issue. -- David C. Rankin, J.D., P.E.

1 0