Estimated read time: 1 minutes
Estimated read time: 2 minutes
today i got this "having subpackages in extra while the main pkg is in the frugalware repo" stuff working. a few notes from the manpage: Special case: subpkgs in other repos.
The situation is the following: you have a package which is in the frugalware repo, but you want its subpackage to be in extra. It's a but tricky, but still possible.
The trick is to create a fake FrugalBuild in the other repo. You could place it whereever you want, but to use repoman you need to place it under $fst/extra/source/subpkgs/pkgname, where pkgname is the name of the original main package.
How to create that fake FrugalBuild?
Copy the original one, but remove everything except the subfoo directives, pkgver and pkgrel. The next step is to clarify which subpackage have to be in which repo. This is done by removing the architectures from the subarchs() array.
Example:
The old main:
subpkgs=('foo' 'bar') subarchs=('i686 x86_64' 'i686 x86_64')
The new main: subpkgs=('foo' 'bar') subarchs=('i686 x86_64' '')
The new fake: subpkgs=('foo' 'bar') subarchs=('' 'i686 x86_64')
This means that bar is expected to be uploaded to extra, while foo is still in the frugal- ware repo. If you move all the subpackages to extra, then of course you can remove the whole subarchs() array from the main FrugalBuild. a few other notes:
- it requires repoman from pacman-tools-0.6.3
- subarchs() is no longer optional
- as the fake FB is not in the current dir, if you record with repoman, it won't record the it!
- i've added subarchs() to the existing packages and updated the skel file :)
- for database generation it needs pacman from darcs, but probably you don't have to care about it as genesis runs that version
Estimated read time: 1 minutes
Estimated read time: 1 minutes
1) just noted xbit's funny boogle skin, and then i figured out how to add some custom metadata without modifying the skin itself. the trick is the "Long Description:" field, so from now there's a short list of links at the right side of this blog
2) something unrelated: the irssi guys noticed our irssi pkg :)
3) ok, this is at least a bit more on-topic: 0.4pre2 released
Estimated read time: 1 minutes
Jan 31 01:16:33 genesis syncpkgd : PWD=/home/syncpkgd ; COMMAND=cp \ /tmp/tmp.HKjbWP /home/ftp/pub/frugalware/frugalware-current/frugalware-x86_64/smb4k-0.6.5-1-x86_64.fpmthe first package built by syncpkgd, the automatic package building daemon
we'll see how much effective it is, the expected performance is that if we push an i686 package, then (if possible) the x86_64 one are uploaded automatically within 4-5 hours :)
Estimated read time: 1 minutes
- finding a way to mute /who
- fixing this redirection stuff in irssi ;)
Estimated read time: 1 minutes
yestreday xorg7 hit -current
in most cases it should install without any problem, if not
pacman -S xorg-fonts xorg-libs --noconfirm
to install all the fonts and libs available- if you're using a binary driver (for example nvidia), try
pacman -R nvidia && pacman -S nvidia
Estimated read time: 1 minutes
slowly but xorg7 is being packaged and if everything works well, it'll hit -current before 0.4pre2. currently you can get the buildscripts, and there are two binary repo:
[xorg7] http://ftp.frugalware.org/pub/other/people/vmiklos/other/xorg7/frugalware-i686and
[xorg7] http://ftp.frugalware.org/pub/other/people/vmiklos/other/xorg7/frugalware-x86_64the buildscripts are available in krix's repo
warning: these pkgs are more unstable than the pkgs usually in -current!
but besiedes some upgrade bugs, it works:
$ X -version:)X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.15-fw1 i686Frugalware Current Operating System: Linux vmobile 2.6.15-fw1 #1 SMP Tue Jan 3 20:46:58 CET 2006 i686 Build Date: 25 January 2006 Before reporting problems, check http://www.frugalware.org to make sure that you have the latest version. Module Loader present
Estimated read time: 1 minutes
man netconfigafter the usual -Syu. huch, it was about 3 days of work :)
Estimated read time: 1 minutes