Sadly, back to chromium

lucabotti — Wed, 26 May 2010 11:47:44 +0000

My day job does not involve Linux or programming, so I usually go around with a netbook as my primary machine.
Sadly, on F13 (which I installed gracefully since beta) Firefox has some performance issue, such as to force me to Chromium. So no weave anymore (weave is awesome) and some support less for the FLOSS world.

Hope Firefox catch back the performance crown, or anyway improve it to be good enough. In the meantime, Chromium is my platform.

Building RPMs, part two – Pinax

lucabotti — Sun, 23 Aug 2009 15:55:33 +0000

Ok, so now we have the environment complete. First thing I want to package is Pinax. This is a nice little collection of Django applications which add some required stuff for most of web based applications.

On the link above you will find all the info for the project, so let’s start. We will build the release version of Pinax (for development versions I have a side project, which I will show you at right time). Please note – all the release used are current for the day this entry has been written.

Download pinax version 0.5.1 from here and put it in rpmbuild/SOURCES. After that:

cd ~/rpmbuild/SPECS

rpmdev-newspec -t python pinax

Rpmdev-newspec creates the skeleton for a new spec file named pinax. The -t python option tells to create a skeleton with some python definitions in it (python definitions are laid out according to this wiki entry on the Fedora Project Wiki); you can see which skeletons are available looking in ‘\etc\rpmdevtools’.

Why Python? Well, my guess is that being DJango a Python framework, you know….

Let’s look at the spec file and put some info into that. You can use any editor for the file (I use geany, fast and lightweight).

# sitelib for noarch packages, sitearch for others (remove the unneeded one)
%{!?python_sitelib: %global python_sitelib %(%{__python} -c “from distutils.sysconfig import get_python_lib; print get_python_lib()”)}
%{!?python_sitearch: %global python_sitearch %(%{__python} -c “from distutils.sysconfig import get_python_lib; print get_python_lib(1)”)}

Name: pinax
Version:
Release: 1%{?dist}
Summary:

Group: Development/Languages
License:
URL:
Source0:
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildArch:
BuildRequires: python-devel

I am assuming that Pinax is a pure python package, so we use the sitelib for noarch packages (first line of the two provided). After that we have to insert some descriptive info of the Pinax project.

But, of course, before going ahead we must check some of the Pinax dependencies.

Continuing tomorrow…

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported.

New Kid in the block….

lucabotti — Thu, 30 Apr 2009 19:29:18 +0000

…is a Samsung NC10, quite an interesting machine, lighter than my laptop (Dell D630).

I was trying to stay clear of these netbooks, but I did not resist. The little one (“atomino“) is currently running with Fedora 11 Preview + updates. Installed without a hitch (not the same with the beta…), only video performance is sub-par and actually under investigation.

I will post my findings. Stay tuned.

Everything technical » Netbook

Sadly, back to chromium

Building RPMs, part two – Pinax

New Kid in the block….