pytony

Yes the problem was that appi used the default system encoding to read files, which is ascii when LANG=C. I assumed encoding should always be utf-8 for these files and explicitly read them with this encoding. If it happens that they may be encoded with a different charset on some systems, I'll have to handle this...

@gissf1 for the record, can you show me the output of the command locale in your system that failed with appi 0.1.6? Thanks

Thanks, I released appi 0.1.7. You can mask 0.1.9999 back and install 0.1.7 when it hit tree. :)

ego query should work fine with python 3.4+, did you face any issue about it?

Can someone try with `appi-0.1.9999` and confirm it fixes the issue? If it does, I'll release it as appi-0.1.7.

It looks like you have your /etc/portage/repos.conf symlinked to /var/git/meta-repo/repos.conf. try: rm /etc/portage/repos.conf rm /var/git/meta-repo/repos.conf/funtoo mkdir /etc/portage/repos.conf/ ln -s /var/git/meta-repo/repos.conf /etc/portage/repos.conf/funtoo for f in /var/git/meta-repo/repos.conf/*.conf; do mv "$f" /etc/portage/repos.conf/; done

It is run automatically after `ego sync` and when you change your profiles using `epro` commands. You normally don't have to run it manually.

`epro update` updates the contents of the file `/etc/portage/make.profile/parent`. This file contains profiles that determine default useflags, masks, make.conf, ... These profiles depend on the python-kit branch you use and profiles you set with epro. `epro update` is indeed missing from documentation. You can file an issue on Jira about it.

It looks like zpools are currently not resizable. :/ If so I think I'd better use LVM on top anyway.

Oh I just found eclean utility by chance and freed 4Go in /usr/portage/distfiles :)

What would prevent you from doing a dual boot with win10?

Thanks Tassie_Tux, I think I'm gonna do a separate `/var` and `/usr/portage/distfiles`. I don't especially need options tuned for mysql performance. This is a database I only use occasionally when I am teleworking. I am currently reading about ZFS. If I understand correctly, I can use ZFS instead of LVM as it ships with its own logical volume manager. However I guess I still need LVM if I want to have distinct filesystems on each volume.

Hi, I'm planning to reinstall Funtoo in order to move to pure64 (as I'm not using any 32bit). Upstream of said reinstall, I think about repartitioning my disks. I would like to leave some space free in order to be able to install LFS aside. I do have one 56GB SSD (sda), one 233GB HDD (sdb) and 1?4GB RAM. My disks are currently partitioned as the following : / -> /dev/sda3 53.5GB /boot -> /dev/sda1 0.5GB swap -> /dev/sda2 2GB /home -> /dev/sdb1 233GB I think about keeping /boot and swap as-is, and split rootfs in 30GB for Funtoo and 23.5GB for LFS However according to df, rootfs already takes 30GB. So I scanned my disk to identify huge folders : /usr (19G) /usr/portage (11G)/usr/portage/distfiles (9.8G) /usr/src (2.8G) /usr/share (2.1G) /usr/lib64 (1.8G) /var (11G)/var/lib (9.7G)/var/lib/mysql (9.5G) Don't you think it would be appropriate to leave /var/lib on its own partition (uppon /dev/sda) ? Or maybe the whole /var directory should be on the HDD rather than on the SSD ? Maybe /usr/portage would also be welcome on its own partition ? If I do this, I guess I will have to setup an initramfs (which I don't have yet). I see it as an opportunity to learn what it is, how it works and why it is needed. If I setup an initramfs, I will take the opportunity to go back to LVM as well (I left LVM in order to get rid of the initramfs when I wanted to focus on the kernel). Finally, I also think about learning more about filesystems and try "unusual" ones. Until now, I've only been using ext[2-4] and XFS. I've heard a lot about ZFS and BtrFS. Unfortunately I don't know much about filesystems (only got a very basic course about FAT, inode-based FS and the differences) and I don't know what changes I will be able to notice and what things I will be able to do with another filesystem. Do you think it is advisable to, let's say, use ZFS for the rootfs and learn more about filesystems a few months later ? Thank you all.

I'm picking up your w!! trick for vim :P mkdir and cd in a row: mkncd() { mkdir -pv $1 cd $1 } In my python virtualenvs (using virtualenvwrapper), I have a postactivate hook to cd in the right directory after "workon virtualenv": [[ -f "$VIRTUAL_ENV/.workpath" ]] && cd $(cat $VIRTUAL_ENV/.workpath)

Now I understand how you can help so many concurrent people at the same time. :P