Debian Packaging

Debian Packaging

[Centurion Computer Technology (2005) Ltd]

Hi,

I plan to spend some time working on the raid/lvm support which seems
rather broken at the moment.  To make this happen I need to be able to
build debian packages directly out of git as the test machines don't
have a dev environment, and I don't want to mess with my workstations
boot process.

Robert, Can you please add the debian packaging specific stuff to the
git repo.

Thanks,
-- 
Daniel Reurich

Centurion Computer Technology (2005) Limited.
Ph: 021 797 722

Re: Debian Packaging

[Robert Millan]

On Tue, Jan 08, 2008 at 08:51:49AM +1300, Centurion Computer Technology (2005) Ltd wrote:
> Hi,
> 
> I plan to spend some time working on the raid/lvm support which seems
> rather broken at the moment.  To make this happen I need to be able to
> build debian packages directly out of git as the test machines don't
> have a dev environment, and I don't want to mess with my workstations
> boot process.

Nice!  This is very needed.

> Robert, Can you please add the debian packaging specific stuff to the
> git repo.

What git repo?

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)

Re: Debian Packaging

[Centurion Computer Technology (2005) Ltd]

On Mon, 2008-01-07 at 23:00 +0100, Robert Millan wrote:
> On Tue, Jan 08, 2008 at 08:51:49AM +1300, Centurion Computer Technology (2005) Ltd wrote:
> > Hi,
> > 
> > I plan to spend some time working on the raid/lvm support which seems
> > rather broken at the moment.  To make this happen I need to be able to
> > build debian packages directly out of git as the test machines don't
> > have a dev environment, and I don't want to mess with my workstations
> > boot process.
> 
> Nice!  This is very needed.
> 
> > Robert, Can you please add the debian packaging specific stuff to the
> > git repo.
> 
> What git repo?
> 

The one Pavel setup at:
	http://repo.or.cz/w/grub2.git
(that's the project's web page, see it for download instructions)


-- 
Daniel Reurich

Centurion Computer Technology (2005) Limited.
Ph: 021 797 722

Re: Debian Packaging

[Robert Millan]

On Tue, Jan 08, 2008 at 11:06:50AM +1300, Centurion Computer Technology (2005) Ltd wrote:
> > > Robert, Can you please add the debian packaging specific stuff to the
> > > git repo.
> > 
> > What git repo?
> > 
> 
> The one Pavel setup at:
> 	http://repo.or.cz/w/grub2.git
> (that's the project's web page, see it for download instructions)

That's a mirror of our CVS, right?  You mean that you want me to add the debian
stuff to CVS, or... ?

I'm sorry but I'm not familiar with git.  I know it supports strange branching
stuff but that's about it :-)

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)

Re: Debian Packaging

[Centurion Computer Technology (2005) Ltd]

On Mon, 2008-01-07 at 23:13 +0100, Robert Millan wrote:
> On Tue, Jan 08, 2008 at 11:06:50AM +1300, Centurion Computer Technology (2005) Ltd wrote:
> > > > Robert, Can you please add the debian packaging specific stuff to the
> > > > git repo.
> > > 
> > > What git repo?
> > > 
> > 
> > The one Pavel setup at:
> > 	http://repo.or.cz/w/grub2.git
> > (that's the project's web page, see it for download instructions)
> 
> That's a mirror of our CVS, right?  You mean that you want me to add the debian
> stuff to CVS, or... ?

Hopefully Pavel can enlighten us on how  this relates to CVS.  I thought
everything was/had moved to git.  I assume that if youa dd it to CVS
then it will be magically replicated in the git repository

> 
> I'm sorry but I'm not familiar with git.  I know it supports strange branching
> stuff but that's about it :-)

For debian there is also cool tools like git-buildpackage which runs the
dbuild process straight out of the git tree and git-dch for updating the
changelog with the comments out of gits commit logs.  Definitely worth a
play.
> 
-- 
Daniel Reurich

Centurion Computer Technology (2005) Limited.
Ph: 021 797 722

Re: Debian Packaging

[Pavel Roskin]

On Tue, 2008-01-08 at 11:26 +1300, Centurion Computer Technology (2005)
Ltd wrote:

> Hopefully Pavel can enlighten us on how  this relates to CVS.  I thought
> everything was/had moved to git.  I assume that if youa dd it to CVS
> then it will be magically replicated in the git repository

There is no magic here.  I just run a simple script from time to time
(it's not even a cron job).  I cannot promise that it will happen
forever.

I suggest that you don't rely on the git repository as it is now.  I
don't want to be in the position that others depend on me running
something every day or on my machine being up and running.

If you really need a git repository, I suggest that you make your own
mirror or take over the mirroring process on repo.or.cz and make it
automatic.  You'll need a user account on repo.or.cz for the later.

Just in case, that's the script I'm using:

#!/bin/sh

GRUB2_GIT_DIR=/home/proski/src/grub2-git
GRUB2_CVS_AUTHORS=/home/proski/local/grub-cvs-authors
GRUB2_CVS_ROOT=:pserver:anoncvs@cvs.savannah.gnu.org:/cvsroot/grub
GRUB2_GIT_REPO=git+ssh://repo.or.cz/srv/git/grub2.git

cd "$GRUB2_GIT_DIR"
git-cvsimport -d "$GRUB2_CVS_ROOT" -C "$GRUB2_GIT_DIR" -k -u -A \
  "$GRUB2_CVS_AUTHORS" -a grub2

git-update-server-info
git-gc --prune
git-push --all "$GRUB2_GIT_REPO"

-- 
Regards,
Pavel Roskin

Re: Debian Packaging

[Robert Millan]

On Tue, Jan 08, 2008 at 11:26:13AM +1300, Centurion Computer Technology (2005) Ltd wrote:
> On Mon, 2008-01-07 at 23:13 +0100, Robert Millan wrote:
> > That's a mirror of our CVS, right?  You mean that you want me to add the debian
> > stuff to CVS, or... ?
> 
> Hopefully Pavel can enlighten us on how  this relates to CVS.  I thought
> everything was/had moved to git.  I assume that if youa dd it to CVS
> then it will be magically replicated in the git repository

Uhm yes, I suppose so.  Well, anyway, I don't think adding the debian directory
to official GRUB CVS is a good idea.  Debian has its own policies, and there
are strong reasons for having the packaging be split from upstream.

Perhaps there's an easier way to archive what you need.  For example, you could
simply grab the latest debian package, and start working from there.  Then you
can revision-control your tree with git;  this worked well for me (I made a
local SVN repository for my own use when working on the LinuxBIOS port).

> > I'm sorry but I'm not familiar with git.  I know it supports strange branching
> > stuff but that's about it :-)
> 
> For debian there is also cool tools like git-buildpackage which runs the
> dbuild process straight out of the git tree and git-dch for updating the
> changelog with the comments out of gits commit logs.  Definitely worth a
> play.

I might have a look when I have some free time.  Just not now :-)

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)

debian packaging

[Mike Turquette]

Hi all,

I'm trying to understand more about debian packaging in OE.  I know
that OE can churn out dpkg's as a result, but does OE have a way to
intelligently make use of source code that has a 'debian' directory
complete with rules and all of that?

By 'intelligently' I mean can OE determine what DEPENDS and RDEPENDS
should be, based on the dpkg control info and can it figure out what
needs to go into staging?  I'm hoping for something analogous to
autotools.bbclass which uses stuff in the source (instead of the
recipe) to figure out much of the configuration and decision-making.

Thanks much,
Mike

Re: debian packaging

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Hi,

Mike Turquette schrieb:
> Hi all,
> 
> I'm trying to understand more about debian packaging in OE.  I know
> that OE can churn out dpkg's as a result, but does OE have a way to
> intelligently make use of source code that has a 'debian' directory
> complete with rules and all of that?
OE's debian packaging has nothing to do with the 'debian' directory.

> By 'intelligently' I mean can OE determine what DEPENDS and RDEPENDS
> should be, based on the dpkg control info and can it figure out what
> needs to go into staging?  I'm hoping for something analogous to
> autotools.bbclass which uses stuff in the source (instead of the
> recipe) to figure out much of the configuration and decision-making.
It is the other way round: By declaring you want .deb as output it will
take a package's RDEPENDS and many other information to create a deb's
control file.

The mamona project has some support for creating debian source packages,
too.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

Re: debian packaging

[Rodrigo Vivi]

On Mon, Feb 9, 2009 at 11:56 PM, Robert Schuster <theBohemian@gmx.net> wrote:
> Hi,
>
> Mike Turquette schrieb:
>> Hi all,

Hi

>>
>> I'm trying to understand more about debian packaging in OE.  I know
>> that OE can churn out dpkg's as a result,

Yes. It is provided by package_deb.bbclass and works very well.

> > but does OE have a way to
>> intelligently make use of source code that has a 'debian' directory
>> complete with rules and all of that?

No. It is very difficult to have something really "intelligent" do
create a complete debian directory to build your sources in a way that
the result is really like the .deb generated by package_deb.bblcass.

Actually in Mamona we have the sourcedsc.bbclass that creates a .dsc
(debian source package) but it has an empty rules. We've just created
it to have an easy way to read sources inside Mamona SDK (which is
chroot based).

We though about lots of ideas to implement sourcedsc.bbclass to
generate a good rules, but we never found an good and easy way to do
that.

> OE's debian packaging has nothing to do with the 'debian' directory.
>
>> By 'intelligently' I mean can OE determine what DEPENDS and RDEPENDS
>> should be, based on the dpkg control info and can it figure out what
>> needs to go into staging?  I'm hoping for something analogous to
>> autotools.bbclass which uses stuff in the source (instead of the
>> recipe) to figure out much of the configuration and decision-making.
> It is the other way round: By declaring you want .deb as output it will
> take a package's RDEPENDS and many other information to create a deb's
> control file.

Actually the control file or depends variable are not the problem. The
most difficult part is to have a good rules debian file.

>
> The mamona project has some support for creating debian source packages,
> too.

http://dev.openbossa.org/mamona/gitweb?p=mamona.git;a=blob;f=classes/sourcedsc.bbclass;h=d5bbc64906c49809fdc43505f3f0cc7ee183b0aa;hb=HEAD

>
> Regards
> Robert
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>

Cheers,

-- 
Rodrigo Vivi
INdT - Instituto Nokia de Tecnologia
Blog: http://blog.vivi.eng.br
GPG: 0x905BE242 @ wwwkeys.pgp.net