Re: [Paco-general] http:// and ftp:// support

[Thomas S. <to...@go...>]

Hi,
hmm, I`m using paco in a little different way.
Let me explain:
Updating a LFS-System is a special thing.
There a packages which are easy to update, other (like glibc, gcc or others) 
are a little bit complicated.
So we were thinking about how to do it a) clean, b) most automatically c) in 
an easy way.

A few years ago we (most work by my friend) started to write a script which do 
all this work,
the script is called "mkpacoball" and it is comparably with pacman from arch 
or pkgtools from Slackware.
It`s building pacoballs in a fakeroot-environment using a configuration-file 
in /etc and a Buildscript (PkgBuild) for each package.
mkpacoball is doing the following things:

It is reading the BuildScript (PkgBuild), creating a temp. Builddirectory 
under /tmp (Build-$$), it downloads the sources from the servers, extracts the 
sources and starts compiling the sources using the "nomal" Options  like --
prefix=/usr, sysconfdir=/etc, localstatedir=/var and so on.
Special Options can be defined in the PkgBuilds.

Maybe a package needs one or more patches the patchsource can be defined in 
the PkgBuild and mkpacoball patches them.

After compiling the sources mkpacoball installs the package to Destdir (under 
Build-$$), strips the binarys what can be enabled/disabled in /etc/mkpacoball) 
and at the end of all mkpacoball is asking for the root-Pwd to deinstall the 
old package and install the update. At least a pacoball will be generated from 
the installed files and will  be stored in a place you can define (take a look 
at the end of mkpacoball, Line 372).

What you need is mkpacoball, mkpacoball.conf (placed under /etc) and PkgBuilds 
for each Packages.

My PkgBuilds are sored under /usr/src/sources/$groups/$pkgname, as example

"/usr/src/sources/devel/boost/PkgBuild".

If there is a new version of boost I navigate to this PkgBuild, change the 
versionnumber in the PkgBuild and start building the package by
"mkpacoball -c -i PkgBuild". Setting an alias in the bashrc or zshenv is a 
good thing to make it easier :-)

mkpacoball depends on fakeroot, lzma/xz, wget, patch, tar, zip/unzip and a few 
other things which should be on each system.

Please let me say that this way of building packages is working here perfectly 
but updateing packages often uses new options and so on, use it on your own 
risk. Over the years I have written a Repo with more than 600 PkgBuilds but 
every toolchain is different. Because of this I do not attach all my 
PkgBuilds. Take a look at all the files, maybe you like it, maybe not :-)
But NO WARRANTY!!! Use it at your own risk!!!
 

If you have other questions about it please let me know, you can contact me 
here or with jabber (sla...@ja...).

Greetings








 





 




Am Donnerstag 03 Juni 2010, 09:30:53 schrieb Nathanael C Higley:
> Sorry about that last msg i forgot to turn off the encryption.
> 
> Well anyway i was wondering if there was any patch to paco-2.0.7
> with the lzma-xz.patch that would allow paco to download from and
> upgrade from http/ftp sites like the slackware-13.0 pkgtools or
> debpkg does?
> 
> ps: Thanks in advance
> 
> 
> ---------------------------------------------------------------------------
> --- ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Paco-general mailing list
> Pac...@li...
> https://lists.sourceforge.net/lists/listinfo/paco-general