[EMAIL PROTECTED] writes:
> > Native debian packages can contain a debian directory since such
> > an application would not make sense on a non-debian system.
>
> How can you make a Debian package without a debian directory? It either
> has to be in the source or the diff. Native packages
> > All pure Debian packages must included a debian directory. Non-native
> > packages may or may not include a debian directory in the upstream
> > source file. (Upstream source is upstream source. If the upstream
> > author provides an old/obsolete debian directory in the upstream tarb=
> all,
[EMAIL PROTECTED] writes:
> All pure Debian packages must included a debian directory. Non-native
> packages may or may not include a debian directory in the upstream
> source file. (Upstream source is upstream source. If the upstream
> author provides an old/obsolete debian directory in the u
> "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
> =20
> > a "pure debian" package as you put it should really only be for items=
> written
> > for debian by debian devels. Anything else can be treated as a stand=
> ard
> > package.
>
> I would add that only pure Debian packages should incl
[EMAIL PROTECTED] writes:
> > Native debian packages can contain a debian directory since such
> > an application would not make sense on a non-debian system.
>
> How can you make a Debian package without a debian directory? It either
> has to be in the source or the diff. Native packages
> > All pure Debian packages must included a debian directory. Non-native
> > packages may or may not include a debian directory in the upstream
> > source file. (Upstream source is upstream source. If the upstream
> > author provides an old/obsolete debian directory in the upstream tarb=
> all
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
> a "pure debian" package as you put it should really only be for items written
> for debian by debian devels. Anything else can be treated as a standard
> package.
I would add that only pure Debian packages should include the 'debian'
direc
[EMAIL PROTECTED] writes:
> All pure Debian packages must included a debian directory. Non-native
> packages may or may not include a debian directory in the upstream
> source file. (Upstream source is upstream source. If the upstream
> author provides an old/obsolete debian directory in the
> "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
> =20
> > a "pure debian" package as you put it should really only be for items=
> written
> > for debian by debian devels. Anything else can be treated as a stand=
> ard
> > package.
>
> I would add that only pure Debian packages should inc
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
> a "pure debian" package as you put it should really only be for items written
> for debian by debian devels. Anything else can be treated as a standard
> package.
I would add that only pure Debian packages should include the 'debian'
dire
Colin Watson:
> Why couldn't you use 'dh_installchangelogs ChangeLog' to achieve the
> same effect?
Because it is a native Debian package, and the manual page for
dh_installchangelogs says
NOTES
It is an error to specify an upstream changelog file for a
debian native package.
--
peter karlsson <[EMAIL PROTECTED]> wrote:
>Manuel Estrada Sainz:
>> The first problem is that I generate the changelog automaticly from CVS
>> which seams too big and verbose for a debian changelog but I am not
>> suposed to have an upstream changelog in a pure debian package.
>
>Well, I "cheat" my
Colin Watson:
> Why couldn't you use 'dh_installchangelogs ChangeLog' to achieve the
> same effect?
Because it is a native Debian package, and the manual page for
dh_installchangelogs says
NOTES
It is an error to specify an upstream changelog file for a
debian native package.
--
peter karlsson <[EMAIL PROTECTED]> wrote:
>Manuel Estrada Sainz:
>> The first problem is that I generate the changelog automaticly from CVS
>> which seams too big and verbose for a debian changelog but I am not
>> suposed to have an upstream changelog in a pure debian package.
>
>Well, I "cheat" m
Manuel Estrada Sainz:
> The first problem is that I generate the changelog automaticly from CVS
> which seams too big and verbose for a debian changelog but I am not
> suposed to have an upstream changelog in a pure debian package.
Well, I "cheat" myself, with both a standard changelog and a Debi
Manuel Estrada Sainz:
> The first problem is that I generate the changelog automaticly from CVS
> which seams too big and verbose for a debian changelog but I am not
> suposed to have an upstream changelog in a pure debian package.
Well, I "cheat" myself, with both a standard changelog and a Deb
> I am packing a program (VisualOS) which I am the author and upstream
> maintainer (pure debian package?) and I have a couple of problems.
As has been stated, this should not be a pure debian package.
For example, I have a package called msttcorefonts which is an installer
app for installing Mic
> I am packing a program (VisualOS) which I am the author and upstream
> maintainer (pure debian package?) and I have a couple of problems.
As has been stated, this should not be a pure debian package.
For example, I have a package called msttcorefonts which is an installer
app for installing Mi
On 22-Mar-2001 Manuel Estrada Sainz wrote:
> Hello all,
>
> I am packing a program (VisualOS) which I am the author and upstream
> maintainer (pure debian package?) and I have a couple of problems.
>
a "pure debian" package as you put it should really only be for items written
for debian by de
Hello all,
I am packing a program (VisualOS) which I am the author and upstream
maintainer (pure debian package?) and I have a couple of problems.
The first problem is that I generate the changelog automaticly from CVS
which seams too big and verbose for a debian changelog but I am not
suposed t
On 22-Mar-2001 Manuel Estrada Sainz wrote:
> Hello all,
>
> I am packing a program (VisualOS) which I am the author and upstream
> maintainer (pure debian package?) and I have a couple of problems.
>
a "pure debian" package as you put it should really only be for items written
for debian by d
Hello all,
I am packing a program (VisualOS) which I am the author and upstream
maintainer (pure debian package?) and I have a couple of problems.
The first problem is that I generate the changelog automaticly from CVS
which seams too big and verbose for a debian changelog but I am not
suposed
22 matches
Mail list logo
