On Thu, Aug 07, 2003 at 12:54:08PM -0700, Eric Winger wrote:
> I hope that I've selected the correct debian mailing list for this
> question. But if not, I would appreciate if you could redirect properly.
Nope, this is the right spot.
> My first steps are proving to be quite haltingly slow. I'm
On Fri, Aug 08, 2003 at 11:24:13AM +0100, Colin Watson wrote:
> On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> > The things which absolutely have to be in a package in order to be
> > built are debian/rules and debian/control. debian/rules gives the
> > commands required to make
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> Ok, I've managed to create a .deb package, experimented with putting
> things in the rules file, installed my package locally. Learned a little
> about purge and kind of have the gist of what y'all have been trying to
> pound into my
On Ter, 2003-08-12 at 14:38, Eric Winger wrote:
> * all the deb-src entries i tried to add to my sources.list give me
> errors when I try to get the source. What is the url for sources? This
> is my latest attempt:
>
> deb-src ftp://ftp.debian.org/debian testing main contrib free
My sources.lis
Hi,
by the way, do you use "debuild" to build your package?
That way Debian will do some more checks before and after build like
build dependencies and lintian runs. Lintian will catch a lot of
little mistakes one can make like having *.ex files still in the
package. Listen to it.
MfG
Go
Eric Winger <[EMAIL PROTECTED]> writes:
> ok, I've managed to make a .deb file & a big ol tarball. Questions:
> * I thought that the .deb file would end up containing all of my
> * files, but the only thing that could possible hold my source is the
> * big tarball that dpkg-buildpackage built for
oops, shouldn't have posted so soon. I found the dpkg -i .deb option.
I'll work through that. sorry
Matthew Palmer wrote:
On Mon, Aug 11, 2003 at 04:16:31PM -0700, Eric Winger wrote:
> thx to all for the responses. I'm slowly making progress here. Could
> someone distinguish the configuration se
Ok, I got a few more things understood including what directories get
built inside of debian, etc. So I think I understand better what is
being installed where, so again, disregard the last email.
I've gotten a package to correctly deliver a .bin to a folder &
successfully run that on install.
Ok, I've managed to create a .deb package, experimented with putting
things in the rules file, installed my package locally. Learned a little
about purge and kind of have the gist of what y'all have been trying to
pound into my head.
But now I've run into a problem. For my first package, which
I've been able to build a package, install it, get a postinst script to
run properly. Now, I'm at the point in my little test where
understanding where everything goes during install is important.
I'm moving away from using New Deb Maintainer docs and trying to follow
advice given in this forum
Eric Winger <[EMAIL PROTECTED]> writes:
> Ahh, this brings up a point that has bothered me about debian. Well
> actually in this case, two points.
>
> * all the deb-src entries i tried to add to my sources.list give me
> * errors when I try to get the source. What is the url for sources?
> * This
Eric Winger wrote:
> would it be sacreligious to ask why sources are kept in non-free?
You are asking an obvious question and the answer is the obvious one.
The sources are in non-free because they are not free. Look at the
copyrights of any of the packages in non-free and you will see that
they
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> I've modified the postinst.ex file, but my commands aren't being
> executed. And the Debian New Maintainers' Guide says I shouldn't do this
> (add to maintainer scripts) yet. So that tells me I should be putting my
> configuration co
should have added that I also tried the fakeroot /debian/rules binary to
build the .deb, but it just told me that it didn't find a file on a line
that didn't exist in my /rules file.
eric
Winger, Eric wrote:
thx to all for the responses. I'm slowly making progress here. Could
someone distingui
ok, I've managed to make a .deb file & a big ol tarball. Questions:
* I would like to test install this package but not go through the
apt-get stuff, because i believe it goes to sources.list etc. Is there a
simple way to simulate this load to see if my commands run successfully?
Or even load t
On Tue, Aug 12, 2003 at 11:53:27AM -0700, Eric Winger wrote:
> Colin Watson wrote:
> >That's correct except that you want "non-free" there, not "free".
> >(Ever think you'd hear a Debian developer say that?)
>
> would it be sacreligious to ask why sources are kept in non-free?
I think one of us
Matthew Palmer wrote:
The easiest way for packages in the actual archive is to run 'apt-get
source
'. That'll download the sources and unpack them into the
current
directory.
Ahh, this brings up a point that has bothered me about debian. Well
actually in this case, two points.
* all the de
Colin Watson wrote:
That's correct except that you want "non-free" there, not "free".
(Ever think you'd hear a Debian developer say that?)
would it be sacreligious to ask why sources are kept in non-free?
I found it easiest (years ago) to read the sources.list(5) man page and
learn how those
On Mon, Aug 11, 2003 at 04:16:31PM -0700, Eric Winger wrote:
> thx to all for the responses. I'm slowly making progress here. Could
> someone distinguish the configuration section and how that applies to
> debian packages for me (the eternal newbie).
There are several "configuration sections" yo
On Tue, Aug 12, 2003 at 10:38:06AM -0700, Eric Winger wrote:
> Matthew Palmer wrote:
> >The easiest way for packages in the actual archive is to run 'apt-get
> >source '. That'll download the sources and unpack them into
> >the current directory.
>
> Ahh, this brings up a point that has bothered
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> Any ideas? Or is the postinst.ex file correct, and i may be not writing
> the script correctly. I just added:
>
> cp myFile /hardcoded path/
> ./path/myFile (wishing to run that file)
.ex stands for example. remove the .ex.
I sugges
Goswin von Brederlow wrote:
Hi,
by the way, do you use "debuild" to build your package?
I'm using dpkg-buildpackage -rfakeroot
That way Debian will do some more checks before and after build like
build dependencies and lintian runs. Lintian will catch a lot of
little mistakes one can make lik
thx to all for the responses. I'm slowly making progress here. Could
someone distinguish the configuration section and how that applies to
debian packages for me (the eternal newbie).
I was under the impression that the configuration rules were what the
package would run after it was loaded. Ho
Ok, I got a few more things understood including what directories get
built inside of debian, etc. So I think I understand better what is
being installed where, so again, disregard the last email.
I've gotten a package to correctly deliver a .bin to a folder &
successfully run that on install.
Goswin von Brederlow wrote:
Hi,
by the way, do you use "debuild" to build your package?
I'm using dpkg-buildpackage -rfakeroot
That way Debian will do some more checks before and after build like
build dependencies and lintian runs. Lintian will catch a lot of
little mistakes one can make
I've been able to build a package, install it, get a postinst script to
run properly. Now, I'm at the point in my little test where
understanding where everything goes during install is important.
I'm moving away from using New Deb Maintainer docs and trying to follow
advice given in this foru
Hi,
by the way, do you use "debuild" to build your package?
That way Debian will do some more checks before and after build like
build dependencies and lintian runs. Lintian will catch a lot of
little mistakes one can make like having *.ex files still in the
package. Listen to it.
MfG
Go
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> Ok, I've managed to create a .deb package, experimented with putting
> things in the rules file, installed my package locally. Learned a little
> about purge and kind of have the gist of what y'all have been trying to
> pound into my
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> I've modified the postinst.ex file, but my commands aren't being
> executed. And the Debian New Maintainers' Guide says I shouldn't do this
> (add to maintainer scripts) yet. So that tells me I should be putting my
> configuration co
On Tue, Aug 12, 2003 at 04:40:42PM -0700, Eric Winger wrote:
> Any ideas? Or is the postinst.ex file correct, and i may be not writing
> the script correctly. I just added:
>
> cp myFile /hardcoded path/
> ./path/myFile (wishing to run that file)
.ex stands for example. remove the .ex.
I sugges
On Tue, Aug 12, 2003 at 11:53:27AM -0700, Eric Winger wrote:
> Colin Watson wrote:
> >That's correct except that you want "non-free" there, not "free".
> >(Ever think you'd hear a Debian developer say that?)
>
> would it be sacreligious to ask why sources are kept in non-free?
I think one of us
Ok, I've managed to create a .deb package, experimented with putting
things in the rules file, installed my package locally. Learned a little
about purge and kind of have the gist of what y'all have been trying to
pound into my head.
But now I've run into a problem. For my first package, which
Eric Winger wrote:
> would it be sacreligious to ask why sources are kept in non-free?
You are asking an obvious question and the answer is the obvious one.
The sources are in non-free because they are not free. Look at the
copyrights of any of the packages in non-free and you will see that
they
Eric Winger <[EMAIL PROTECTED]> writes:
> ok, I've managed to make a .deb file & a big ol tarball. Questions:
> * I thought that the .deb file would end up containing all of my
> * files, but the only thing that could possible hold my source is the
> * big tarball that dpkg-buildpackage built for
oops, shouldn't have posted so soon. I found the dpkg -i .deb option.
I'll work through that. sorry
Matthew Palmer wrote:
On Mon, Aug 11, 2003 at 04:16:31PM -0700, Eric Winger wrote:
> thx to all for the responses. I'm slowly making progress here. Could
> someone distinguish the configuration
ok, I've managed to make a .deb file & a big ol tarball. Questions:
* I would like to test install this package but not go through the
apt-get stuff, because i believe it goes to sources.list etc. Is there a
simple way to simulate this load to see if my commands run successfully?
Or even load
Eric Winger <[EMAIL PROTECTED]> writes:
> Ahh, this brings up a point that has bothered me about debian. Well
> actually in this case, two points.
>
> * all the deb-src entries i tried to add to my sources.list give me
> * errors when I try to get the source. What is the url for sources?
> * This
Colin Watson wrote:
That's correct except that you want "non-free" there, not "free".
(Ever think you'd hear a Debian developer say that?)
would it be sacreligious to ask why sources are kept in non-free?
I found it easiest (years ago) to read the sources.list(5) man page and
learn how th
On Ter, 2003-08-12 at 14:38, Eric Winger wrote:
> * all the deb-src entries i tried to add to my sources.list give me
> errors when I try to get the source. What is the url for sources? This
> is my latest attempt:
>
> deb-src ftp://ftp.debian.org/debian testing main contrib free
My sources.lis
On Tue, Aug 12, 2003 at 10:38:06AM -0700, Eric Winger wrote:
> Matthew Palmer wrote:
> >The easiest way for packages in the actual archive is to run 'apt-get
> >source '. That'll download the sources and unpack them into
> >the current directory.
>
> Ahh, this brings up a point that has bothered
Matthew Palmer wrote:
The easiest way for packages in the actual archive is to run 'apt-get
source
'. That'll download the sources and unpack them into the
current
directory.
Ahh, this brings up a point that has bothered me about debian. Well
actually in this case, two points.
* all the
> Will the packaging tools complain if you have no copyright file, too? I
> know it's necessary for uploading, of course, and I'm sure lintian would
> have a right whinge, but will (eg) debhelper scripts have a complain, to
> your knowledge?
Nope. Neither dpkg-* nor debhelper will complain. (Tried
On Mon, Aug 11, 2003 at 04:16:31PM -0700, Eric Winger wrote:
> thx to all for the responses. I'm slowly making progress here. Could
> someone distinguish the configuration section and how that applies to
> debian packages for me (the eternal newbie).
There are several "configuration sections" yo
should have added that I also tried the fakeroot /debian/rules binary to
build the .deb, but it just told me that it didn't find a file on a line
that didn't exist in my /rules file.
eric
Winger, Eric wrote:
thx to all for the responses. I'm slowly making progress here. Could
someone distin
thx to all for the responses. I'm slowly making progress here. Could
someone distinguish the configuration section and how that applies to
debian packages for me (the eternal newbie).
I was under the impression that the configuration rules were what the
package would run after it was loaded. H
On Fri, Aug 08, 2003 at 10:12:52PM +1000, Matthew Palmer wrote:
> On Fri, Aug 08, 2003 at 11:24:13AM +0100, Colin Watson wrote:
> > On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> > > The things which absolutely have to be in a package in order to be
> > > built are debian/rules a
On Fri, Aug 08, 2003 at 10:12:52PM +1000, Matthew Palmer wrote:
> On Fri, Aug 08, 2003 at 11:24:13AM +0100, Colin Watson wrote:
> > On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> > > The things which absolutely have to be in a package in order to be
> > > built are debian/rules a
> Will the packaging tools complain if you have no copyright file, too? I
> know it's necessary for uploading, of course, and I'm sure lintian would
> have a right whinge, but will (eg) debhelper scripts have a complain, to
> your knowledge?
Nope. Neither dpkg-* nor debhelper will complain. (Tried
On Fri, Aug 08, 2003 at 11:24:13AM +0100, Colin Watson wrote:
> On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> > The things which absolutely have to be in a package in order to be
> > built are debian/rules and debian/control. debian/rules gives the
> > commands required to make
On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> The things which absolutely have to be in a package in order to be
> built are debian/rules and debian/control. debian/rules gives the
> commands required to make the package, and debian/control has the
> information necessary to na
On Thu, Aug 07, 2003 at 12:54:08PM -0700, Eric Winger wrote:
> I hope that I've selected the correct debian mailing list for this
> question. But if not, I would appreciate if you could redirect properly.
Nope, this is the right spot.
> My first steps are proving to be quite haltingly slow. I'm
On Fri, Aug 08, 2003 at 07:38:11PM +1000, Matthew Palmer wrote:
> The things which absolutely have to be in a package in order to be
> built are debian/rules and debian/control. debian/rules gives the
> commands required to make the package, and debian/control has the
> information necessary to na
Eric Winger wrote:
> So two questions, does the source package need to be raw code or is it
> specific term to refer to a C source filled directory? And two, is my
> goal reasonable for a first-timer?
No, technically the source package is just the combination of upstream
distribution and debian mod
Eric Winger wrote:
> So two questions, does the source package need to be raw code or is it
> specific term to refer to a C source filled directory? And two, is my
> goal reasonable for a first-timer?
No, technically the source package is just the combination of upstream
distribution and debian mod
54 matches
Mail list logo
