Re: .changes files without source packages
Thanks again for everyone's help on this!
For now I'll try generating the changes file by script as we are
building the deb packages through the OpenEmbedded build system and it
handles the actual packaging for us. In the future I'll look at
getting it to build these packages the right way so that they can be
policy compliant, even though we don't plan to ever get them added to
the Debian archive.
On Sun, Dec 5, 2010 at 11:43 PM, Raphael Hertzog <hertzog@debian.org> wrote:
> On Sun, 05 Dec 2010, Paul Wise wrote:
>> On Sun, Dec 5, 2010 at 5:03 AM, Raphael Hertzog <hertzog@debian.org> wrote:
>>
>> > Using dpkg -b directly is still not the right way to build a package.
>> > If you don't want to distribute a source package, that's fine don't
>> > distribute it. But a debian binary package should always be built from
>> > source package, it's the best way to create a policy compliant package
>> > because you will use the same tools that all Debian developers are using
>> > to create official packages.
>> >
>> > And then you will have no problem with dpkg-genchanges... it's only
>> > designed to work from within an unpacked source package.
>>
>> It is very unlikely Daniel's work is intended for the Debian archive,
>> so there is no need for him to create packages in policy compliant,
>> normal or standard way.
>
> Debian policy compliant is our definition of a "good package". And I bet
> everybody wants to create good packages.
>
> So let me disagree with you on this one. :-)
>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Follow my Debian News ▶ http://RaphaelHertzog.com (English)
> ▶ http://RaphaelHertzog.fr (Français)
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 20101206074321.GB32187@rivendell.home.ouaza.com">http://lists.debian.org/[🔎] 20101206074321.GB32187@rivendell.home.ouaza.com
>
>
Reply to: