Frank Küster wrote:
You should try to separate non-debian-specific and debian-specific
parts, IMO.
I have been trying to keep to standard Bourne Shell so it should be ok.
I will try to package it in a normal tar file with (bin, etc, etc)
not exist or something like this. I ended up having to
Frank Küster wrote:
You should try to separate non-debian-specific and debian-specific
parts, IMO.
I have been trying to keep to standard Bourne Shell so it should be ok.
I will try to package it in a normal tar file with (bin, etc, etc)
not exist or something like this. I ended up having to put A
Bengt Thuree <[EMAIL PROTECTED]> wrote:
>> That depends on the complexity of the installation. In most cases,
>> it is
>> highly advisable to have a separate Makefile that does the compilation
>> and installation, and in debian/rules you only call it with appropriate
>> targets and arguments.
> ok
Bengt Thuree <[EMAIL PROTECTED]> wrote:
>> That depends on the complexity of the installation. In most cases,
>> it is
>> highly advisable to have a separate Makefile that does the compilation
>> and installation, and in debian/rules you only call it with appropriate
>> targets and arguments.
> ok
>>> for the buppo --version output. And I think it would be handled by cvs
>> or subversion, but for the moment I am actually using .deb as my
>> revision control
>
> OK, so you do actually want to have your version information generated
> automatically from your revision control stuff.
:-) Th
On Tue, Jun 08, 2004 at 09:01:34AM +0900, Bengt Thuree wrote:
> >The version of the debian package you produce is taken from the package's
> >topmost changelog entry. For timestamps, you can use touch(1), but I'm
> >having trouble coming up with why you'd want to stamp a file to a
> >particular
>
>>> for the buppo --version output. And I think it would be handled by cvs
>> or subversion, but for the moment I am actually using .deb as my
>> revision control
>
> OK, so you do actually want to have your version information generated
> automatically from your revision control stuff.
:-) Th
Matthew Palmer wrote:
want to move some files in your debian/rules file - a typical example
would be moving some scripts to
debian/tmp/usr/share/doc/$packagename/examples.
You don't use dh_installdirs for that, you use dh_installexamples.
I managed to use this one :)
*) Should I list
Hej Frank,
and thank you for very much appreciated comments.
I will try to answer them below
/Bengt
Frank Küster wrote:
Did you read the new maintainers guide and the developers' reference?
Yes, I read them once, twice, and ten times, but must have some problem
with my english apperantly.
On Tue, Jun 08, 2004 at 09:01:34AM +0900, Bengt Thuree wrote:
> >The version of the debian package you produce is taken from the package's
> >topmost changelog entry. For timestamps, you can use touch(1), but I'm
> >having trouble coming up with why you'd want to stamp a file to a
> >particular
>
On Mon, Jun 07, 2004 at 05:17:45PM +0200, Frank K?ster wrote:
> In debian/dirs, you only list the directories that you want to create
> with dh_installdirs - e.g. directories that the upstream Makefiles
> assumes to be present upon installation, or directories to which you
> want to move some files
Matthew Palmer wrote:
want to move some files in your debian/rules file - a typical example
would be moving some scripts to
debian/tmp/usr/share/doc/$packagename/examples.
You don't use dh_installdirs for that, you use dh_installexamples.
I managed to use this one :)
*) Should I list the conffil
Hej Frank,
and thank you for very much appreciated comments.
I will try to answer them below
/Bengt
Frank Küster wrote:
Did you read the new maintainers guide and the developers' reference?
Yes, I read them once, twice, and ten times, but must have some problem
with my english apperantly.
That de
On Mon, Jun 07, 2004 at 05:17:45PM +0200, Frank K?ster wrote:
> In debian/dirs, you only list the directories that you want to create
> with dh_installdirs - e.g. directories that the upstream Makefiles
> assumes to be present upon installation, or directories to which you
> want to move some files
Bengt Thuree <[EMAIL PROTECTED]> schrieb:
> Hej
>
> I have just created one of my first debian package, and would like to
> have some comments on the actual packaging.
Did you read the new maintainers guide and the developers' reference?
>
> Have I missed something?
> I am very confused of
> *)
Bengt Thuree <[EMAIL PROTECTED]> schrieb:
> Hej
>
> I have just created one of my first debian package, and would like to
> have some comments on the actual packaging.
Did you read the new maintainers guide and the developers' reference?
>
> Have I missed something?
> I am very confused of
> *)
Hej
I have just created one of my first debian package, and would like to
have some comments on the actual packaging.
Have I missed something?
I am very confused of
*) Should I only use the rules file, or a separate Makefile
*) Should I list all the directories in the dirs (including /usr/sbin
Hej
I have just created one of my first debian package, and would like to
have some comments on the actual packaging.
Have I missed something?
I am very confused of
*) Should I only use the rules file, or a separate Makefile
*) Should I list all the directories in the dirs (including /usr/sbin)
*
18 matches
Mail list logo