April 2009 - arch-haskell

Arch Linux Haskell Logo
by Xyne 25 Apr '09

25 Apr '09

Hi all, I just wanted to share my attempt at an Arch Linux Haskell logo with you. I've attached both the svg and a 256x256 png file. There's a thread about it on the Arch forum here: http://bbs.archlinux.org/viewtopic.php?id=70945 Feel free to use it and improve it. If someone else has already created a logo, just let me know. I apologize if this is completely outside the focus of this list. Regards, Xyne

1 0

Re: [arch-haskell] ghc-6.10.2 in testing
by Vesa Kaihlavirta 25 Apr '09

25 Apr '09

Excerpts from Peter Hercek's message of Thu Apr 09 14:00:05 +0300 2009: > Vesa Kaihlavirta wrote: > But if we assume that unregister.sh files can contain only "ghc-pkg > unregister" calls then there is no need to even call them. The new ghc > will come with a new/pristine package.conf. Still I would like if you > could save off a copy of the pristine package.conf when installing ghc. > Then I could check in robust way what I installed on top of clean ghc. A > postinstall step like "cd /usr/lib/ghc-<ver>; cp package.conf > package.conf.asInstalled". Yes, that's what I've wondered about too, actually. I like your suggestion. And we can use pacman's configuration file handling instead of rolling our own. 6.10.2-2 postponed then a bit more :) I hope I can get this out soon, because I'll be on vacation until the 19th, and away from my x86_64 box. --vk

3 5

Re: [arch-haskell] ghc-6.10.2 in testing
by Vesa Kaihlavirta 09 Apr '09

09 Apr '09

Excerpts from Peter Hercek's message of Thu Apr 09 13:27:44 +0300 2009: > Vesa Kaihlavirta wrote: > > Another potential issue: > > > > Imagine one of the uninstall.sh scripts having something nasty like the > > unimaginative rm -rf /. > > > > Is this an acceptable risk > Hi Vesa, > > I hope you meant "rm -rf ./" otherwise removing root directory > recursively would not be acceptable at all :) Yes, I meant a situation where somebody had managed to put something harmful in your /usr/share/haskell/foobar/unregister.sh. And the new ghc package executes them all before upgrading, as root of course. --vk

1 0

ghc-6.10.2 in testing
by Vesa Kaihlavirta 08 Apr '09

08 Apr '09

Hey, The new ghc is just a simple verbump at least for now. It doesn't try to do anything intelligent for your cabalized or cabal2arch packages, so all those do break. I'm interested in ideas how to mitigate these issues... now, it seems to me that they cannot very much, and the most we can do is unregister everything prior to upgrading and informing the user of this. Also, none of the community packages are built against this yet, so those will break as well. --vk

4 6