alright, i think i'm basically set up but just have one more question
to ask. i jsut want to make sure i'm going about everything right.
for testing i backported deskbar-applet as follows, was just wondering
if i was missing anything or what not (i;m obviously new at packaging)
got my chroot via pbuilder.
login to the chroot.
apt-get build-dep deskbar-applet
apt-get source deskbar-applet (fetches all sources from dapper repos)
cd deskbar-applet-x.x/
dpkg-buildpackage -d
leaves me with the .deb, pending ant errors of course.
anything else? any suggestions? whats the procedure once the build
completes and everything works fine? just notify the list to have
someone "official" build it or what?
thanks for the help again.
matt nicholson
[EMAIL PROTECTED]
sjoeboo.com
On Nov 30, 2005, at 10:00 AM, matthew nicholson wrote:
excelent, exactly what i needed to here.
On Wed, 2005-11-30 at 09:55 -0500, John Dong wrote:
On 11/30/05, matthew nicholson <[EMAIL PROTECTED]> wrote:
hmm, okay. one question regarding pbuilder/ubp-build.py. if
your using
ubp-build.py inside the pbuilder chroot..how do you fetch the
dapper
source packages? do you just do it by hand, or can you change
where teh
sources are fetch from, so its all automatic?
You don't use ubp-build.py inside pbuilder... ubp-build.py
accomplishes tasks similar to pbuilder, with you in command instead of
pbuilder inside the chroot.
Either way, configuration of sources is done by adding deb-src lines
for Dapper, whether it's /etc/apt/sources.list inside the chroot or
the pbuilder config file.
thanks for the help getting set up guys.
matt nicholson
[EMAIL PROTECTED]
sjoeboo.com
On Wed, 2005-11-30 at 09:19 -0500, John Dong wrote:
meh, either way is fine... I've just never really caught on
to
pbuilder... At times I appreciate the speed of the
unpack-and-hack
approach to figuring out what it takes for a package to
start
compiling...
I've been playing with Device Mapper's Copy-on-Write
functionality for
making all changes to the chroot temporary.
On 11/30/05, Marc Wiriadisastra <[EMAIL PROTECTED]>
wrote:
On 11/30/05, John Dong <[EMAIL PROTECTED]> wrote:
google ubp-build.py....
I run ubp-build.py inside a chroot, which is
cleaned fairly
frequently.
As
long as you don't do stupid things to the chroot,
it'll
stay fairly
clean...
How about using PBuilder? it guarantees a clean
chroot, and
is really
handy to use. See
http://wiki.ubuntu.com/PbuilderHowto for
instructions
+1 from me since I've never had any issues with
pbuilder and
it's create
for testing out dependancy's.
--
ubuntu-backports mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
--
matthew nicholson < [EMAIL PROTECTED]>
sjoeboo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBDjbt3IIMh34W/OGsRAv01AKDncTpkIt1M5iAaGcMY6Mvwp9GdewCg5qfA
uSBTnV+4faTo4kEU9mqiLWk=
=e4ch
-----END PGP SIGNATURE-----
--
ubuntu-backports mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
--
matthew nicholson <[EMAIL PROTECTED]>
sjoeboo.com
--
ubuntu-backports mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
--
ubuntu-backports mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
