You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2008-03-23 13:49:59
- okar
- Member
- Registered: 2008-03-01
- Posts: 12
building packages
arch packages are just tarballs containing the files to be installed(with the package been the root), a PKGINFO file and a list of all files, right?(and maybe a INSTALL file)
If I got the binaries of a package, I can just make an archive of them plus the stuff mentioned above?
is makepkg only usefull when I got a source tarball? or are there advantages in using it for binaries?(is that possible at all)
ty
Offline
#2 2008-03-23 14:01:34
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,487
- Website
Re: building packages
It is easier just to use makepkg to do the packaging rather than addin the PKGINFO etc yourself. For example of how it is done look at the skype PKGBUILD in community: http://cvs.archlinux.org/cgi-bin/viewcv … vsroot=AUR
Offline
#3 2008-03-23 18:36:34
- okar
- Member
- Registered: 2008-03-01
- Posts: 12
Re: building packages
ok thank you,
the package that makepkg has created doesn't contain a .FILELIST, i thought that pacman uses this list when remooving stuff.
is that ok?
Offline
#4 2008-03-23 18:57:30
- Sigi
- Member
- From: Thurgau, Switzerland
- Registered: 2005-09-22
- Posts: 1,131
Re: building packages
I think that this has changed around pacman 3, but I'm not really sure about that.
edit: to be more precise: what has changed is that makepkg no longer creates those files, which is fine. (Still "as far as I remember")
Last edited by Sigi (2008-03-23 18:59:26)
Haven't been here in a while. Still rocking Arch. 
Offline
#5 2008-03-23 21:06:48
- okar
- Member
- Registered: 2008-03-01
- Posts: 12
Re: building packages
in the pacman DB is a list of all files,
so it will probably be created automatically in the installation process.
thx
Offline
Pages: 1