Re: Creating Source Packages
>
> Take a look at
> http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#native_vs_non_native
> and the question after that ("What's wrong with upstream shipping a debian/
> directory?").
>
Yep, all sound like good reasons to separate the source distfile and the
debian specific data.
Currently my package is not suitable for inclusion in Debian, there will
be a lot of work needed in order to achieve this. I am merely after a
single .deb file i can place on sourceforge for the moment that people
can use to install my software, and a source package is helpful in case
someone requests it too.
For convenience I have not separated the debian specific data from the
source for the moment, but thanks for the info I will get around to it
eventually.
I think i might start a new thread to ask about breaking up and
organising my package a bit better.
Thanks,
Brendon.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
On Sunday 29 July 2007, Ben Finney wrote: > Brendon Costa <[EMAIL PROTECTED]> writes: > > I have those files listed below (Excepting the > > package_1.0-1.diff.gz) as there are no differences that need to be > > applied for debian. So a "source distribution" would just include > > the .dsc and .tar.gz file. > > Even when you are acting in both the "upstream" and "Debian packager" > role, you should ensure the foo_1.0.orig.tar.gz contains only the > source for the package, *not* the Debian-specific stuff; and apply the > Debian-specific changes in a foo_1.0-1.diff.gz patch. > > This way your source tarball is more useful to people not using > Debian, or those who want to package your source for a different > distribution. I also share that opinion, but some do not (#388394) providing pointless arguments. Another advantage of having a non-native package is the orig.tar.gz only has to be uploaded once for every upstream release, and whenever you change something to the packaging of same upstream version and bump up the debian revision, you only need to upload the diff.gz to the archives. -- pub 4096R/0E4BD0AB 2003-03-18 fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
Brendon Costa <[EMAIL PROTECTED]> writes: > I have those files listed below (Excepting the > package_1.0-1.diff.gz) as there are no differences that need to be > applied for debian. So a "source distribution" would just include > the .dsc and .tar.gz file. Even when you are acting in both the "upstream" and "Debian packager" role, you should ensure the foo_1.0.orig.tar.gz contains only the source for the package, *not* the Debian-specific stuff; and apply the Debian-specific changes in a foo_1.0-1.diff.gz patch. This way your source tarball is more useful to people not using Debian, or those who want to package your source for a different distribution. -- \ "If [a technology company] has confidence in their future | `\ ability to innovate, the importance they place on protecting | _o__) their past innovations really should decline." -- Gary Barnett | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
On Sun, Jul 29, 2007 at 02:59:53PM +1000, Brendon Costa wrote:
> > Actually, there is no one-file source package form of a deb like there
> > is for rpms. When you create your binary package, a signed .dsc file is
> > created with which you can create the deb in conjunction with the
> > original upstream tarball and the diff of the debian packaging.
>
> Ahh that would have been my mistake. I thought there would have been a
> single .deb file that contained the source package similar to that of
> source rpm's.
>
> I have those files listed below (Excepting the package_1.0-1.diff.gz) as
> there are no differences that need to be applied for debian. So a
> "source distribution" would just include the .dsc and .tar.gz file.
Take a look at
http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#native_vs_non_native
and the question after that ("What's wrong with upstream shipping a debian/
directory?").
- Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
> Actually, there is no one-file source package form of a deb like there > is for rpms. When you create your binary package, a signed .dsc file is > created with which you can create the deb in conjunction with the > original upstream tarball and the diff of the debian packaging. > Ahh that would have been my mistake. I thought there would have been a single .deb file that contained the source package similar to that of source rpm's. I have those files listed below (Excepting the package_1.0-1.diff.gz) as there are no differences that need to be applied for debian. So a "source distribution" would just include the .dsc and .tar.gz file. Thanks, Brendon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
On Sun, Jul 29, 2007 at 11:13:06AM +1000, Brendon Costa wrote: > I have been looking on the web, but have found little in the way of > tutorials on how to create a debian source package. I have created a > binary package for my project (EDoc++: http://edoc.sourceforge.net/), > but want to create a source package and then build the binary one from this. > > Does anyone here know of a link where there is information on doing this > sort of thing? I couldn't believe google didn't come up with anything as > I am sure this is a VERY common way of creating debian packages. It's *really* common -- pretty much every upload into Debian has to provide the source package. You just run 'dpkg-buildpackage -S' in the unpacked tree and it'll do all the usual "dpkg-buildpackage" kind of things and produce a source package including a .changes file. If you want to get a bit lower level, 'dpkg-source -b ' will just build the diff/dsc. Manpages, as usual, will give you all the dirty details. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
Brendon Costa <[EMAIL PROTECTED]> writes:
> I have been looking on the web, but have found little in the way of
> tutorials on how to create a debian source package. I have created a
> binary package for my project (EDoc++:
> http://edoc.sourceforge.net/), but want to create a source package
> and then build the binary one from this.
The "source package" for the 'foo' package, version 1.2 debian release
3, consists of three files:
- 'foo_2.0.orig.tar.gz', the original tarball
- 'foo_2.0-3.diff.gz', the patch file for the Debian changes
- 'foo_2.0-3.dsc', the source control file
See the Debian maintainer's guide ('aptitude install maint-guide', or
choose one of the translation packages).
--
\ "Are you pondering what I'm pondering?" "Umm, I think so, |
`\Brain, but what if the chicken won't wear the nylons?" -- |
_o__)_Pinky and The Brain_ |
Ben Finney
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating Source Packages
On Sun, Jul 29, 2007 at 11:13:06AM +1000, Brendon Costa wrote: > I have been looking on the web, but have found little in the way of > tutorials on how to create a debian source package. I have created a > binary package for my project (EDoc++: http://edoc.sourceforge.net/), > but want to create a source package and then build the binary one from this. > > Does anyone here know of a link where there is information on doing this > sort of thing? I couldn't believe google didn't come up with anything as > I am sure this is a VERY common way of creating debian packages. Actually, there is no one-file source package form of a deb like there is for rpms. When you create your binary package, a signed .dsc file is created with which you can create the deb in conjunction with the original upstream tarball and the diff of the debian packaging. So you would basically distribute the following files: package_1.0-1.dsc package_1.0.orig.tar.gz package_1.0-1.diff.gz And extract/build the package with: $ dpkg-source -x package_1.0-1.dsc $ cd package-1.0 $ debuild I hope this is the way you created your deb in the first place. ;) Cheers, Franz -- .''`. Franz Pletz <[EMAIL PROTECTED]> - http://franz-pletz.org/ : :' : `. `'Always listen to experts. They'll tell you what can't be `- done, and why. Then do it. -- Robert A. Heinlein signature.asc Description: Digital signature
Creating Source Packages
Hi all, I have been looking on the web, but have found little in the way of tutorials on how to create a debian source package. I have created a binary package for my project (EDoc++: http://edoc.sourceforge.net/), but want to create a source package and then build the binary one from this. Does anyone here know of a link where there is information on doing this sort of thing? I couldn't believe google didn't come up with anything as I am sure this is a VERY common way of creating debian packages. Thanks, Brendon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
