23 Feb
2012
23 Feb
'12
4:45 p.m.
On 02/23/2012 11:30 AM, David C. Rankin wrote:
On 02/23/2012 09:44 AM, Baho Utot wrote:
you should also pass the -c option to makechrootpkg so that the
devtools clean the chroot for every package.
That way you can not get unintended dependencies.
This may be of some value to you then ( from my build scripts)
_chroot="/home/chroot"
_path=${0%/*} # fetch directory name = module name
_repos="/home/chroot/root/repo"
cd ${_path}
rm build.log namcap.log filelist.log || true
# update chroot and build package
echo "Building---> ${_path}"
( sudo /usr/sbin/mkarchroot -u ${_chroot}/root |& tee build.log )
( sudo /usr/sbin/makechrootpkg -c -r ${_chroot} |& tee -a build.log )
# Namcap package
_pkg=$(echo *.pkg.*)
[ -f ${_pkg} ] || ( echo "Missing package: ${_pkgname}";exit 4 )
( /usr/bin/namcap ${_pkg} |& tee namcap.log )
# Create list of files in package
( /bin/tar -tf ${_pkg} |& tee filelist.log )
# Me and my repo
mv -vf ${_pkg} ${_repos}
/usr/bin/repo-add ${_repos}/local.db.tar.gz ${_repos}/${_pkg}
exit 0
On 02/23/2012 10:26 AM, Calvin Morrison wrote:
> On 23 February 2012 10:22, David C. Rankin
> <drankinatty(a)suddenlinkmail.com> wrote:
>> On 02/23/2012 09:11 AM, Calvin Morrison wrote:
>>> better - it should just follow the default toolbar icons size as set
>>> in appearance -> icons
>>>
>> I removed it and updated the md5sum for patches.tar.bz2 and I've kicked
off
>> the build again. That is the WORST shortcoming of building in an archroot with
>> an out-of-source build!
>>
>> You can't simply issue a 'makepkg -R'. Suck having to rebuild the
whole
>> tdebase package for a packaging issue after the source is 100% complete!
>>
>> Oh well - 9% and kicking...
>>
>> --
>> David C. Rankin, J.D.,P.E.
>>
> you can with sometimes avoid a rebuild, say you just need to bump a
> version number or add a depend
>
> --noextract basically won't delete src/ and that should let the
> build files remain.
>
>
Just like Baho says, when you are building in a chroot (which you must if
your
packages will be used by someone other than you), then there is no way to pass
custom parameters to makepkg:
https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chro…
No not easily when using a chroot. makechrootpkg
-c -r cleans the environment
every time.
I set up a chroot specifically for Trinity building and start with
Qt3/TQt3
and progress using:
sudo makechrootpkg -r $CHROOT -u
or just
sudo makechrootpkg -r $CHROOT (to avoid the pacman -Syu call)
then manually install the packages:
sudo makechrootpkg -r $CHROOT -I tde-package.tar.xz
then I manually copy the file to the $CHROOT/root/repo and do a repo-add to
update the repo.
If something significant changes in a package, then I rebuild the effected
package and start again with a fresh cleaned $CHROOT and rebuild from that point
on with the [local] repo providing all the dependencies needed.
I would drop the trinity part from above
tdebase-VERSION.tar.xz is good enough
If you are using a scripted systems which you
should be then you have to alter
the scripts which just is not worth doing, so one just reruns the scripts and
waits.
Yup!
But FINALLY!!!
==> Finished making: trinity-tdebase 3513-7 (Thu Feb 23 15:45:42 UTC 2012)
The pkgbuild source package is here:
http://www.3111skyline.com/dl/dt/trinity/arch/src/trinity-tdebase.tar.gz