"Steve M. Robbins" <[EMAIL PROTECTED]> writes:
> Well, for starters, he said the software is "an official GNU project",
> not something written specifically for Debian.
"Debian native", does, in my definition, not imply that the project
must be mainly intended to run on Debian.
Policy is not ver
[EMAIL PROTECTED] writes:
> When the upstream developer and the debian developer are the same person,
> it still makes sense to treat the package as a non-native package if
> there will ever be non-Debian releases.
Ok, this only makes sense if (and as long as) you are both Debian
mainainer and le
Hello fellow developers,
I wonder how strict is the "about 50 characters or so" limitation on the
short description for a debconf template is?
I ask this because some translators seem to be fond of tacking long things
in there. This has happened to some fetchmail templates, for example.
Should
On Wednesday 02 May 2001 10:28, Robert Bihlmeyer wrote:
> [EMAIL PROTECTED] writes:
> > When the upstream developer and the debian developer are the same person,
> > it still makes sense to treat the package as a non-native package if
> > there will ever be non-Debian releases.
>
> Ok, this only ma
Hi all, well that's my situation:
I'm the developer of nettoe, a console based
tic-tac-toe game playable over a network.
available at: http://nettoe.sourceforge.net
Now, I'd really like to see it in the Debian
distribution so I'm just trying to understand
how I can make it possible.
I have just
On Tue, May 01, 2001 at 10:33:39PM +1000, Drew Parsons wrote:
> Thanks for your responses, all :)
>
> Setting the file permissions properly seems to be the main need for the root
> build environment.
A lot of packages used to test for root access in the clean target too.
That was standard practis
On Thu, May 03, 2001 at 08:23:19AM +1000, Hamish Moffatt wrote:
> A lot of packages used to test for root access in the clean target too.
> That was standard practise before we had fakeroot.
>
> I suppose when you were building as root (non-fake), you would end up
> with directories owned by root,
> Now, I'd really like to see it in the Debian
> distribution so I'm just trying to understand
> how I can make it possible.
Do you want to become a debian developer or do you want someone else to
maintain the package?
If you're interested in being a dd, you should apply. Follow the
instructions
i'd like to package the opengl manpages... but there tarballs are a bit
strange... they're .Z files to begin with, and they don't appear to have
a version number (some other docs have 1.2 as a version, so i suppose i
can assume this) and the files untar into a directory called
"release". I'm guessi
> i'd like to package the opengl manpages... but there tarballs are a bit
> strange... they're .Z files to begin with, and they don't appear to have
> a version number (some other docs have 1.2 as a version, so i suppose i
> can assume this) and the files untar into a directory called
> "release".
"Steve M. Robbins" <[EMAIL PROTECTED]> writes:
> Well, for starters, he said the software is "an official GNU project",
> not something written specifically for Debian.
"Debian native", does, in my definition, not imply that the project
must be mainly intended to run on Debian.
Policy is not ve
[EMAIL PROTECTED] writes:
> When the upstream developer and the debian developer are the same person,
> it still makes sense to treat the package as a non-native package if
> there will ever be non-Debian releases.
Ok, this only makes sense if (and as long as) you are both Debian
mainainer and l
Hello fellow developers,
I wonder how strict is the "about 50 characters or so" limitation on the
short description for a debconf template is?
I ask this because some translators seem to be fond of tacking long things
in there. This has happened to some fetchmail templates, for example.
Should
On Wednesday 02 May 2001 10:28, Robert Bihlmeyer wrote:
> [EMAIL PROTECTED] writes:
> > When the upstream developer and the debian developer are the same person,
> > it still makes sense to treat the package as a non-native package if
> > there will ever be non-Debian releases.
>
> Ok, this only m
Hi all, well that's my situation:
I'm the developer of nettoe, a console based
tic-tac-toe game playable over a network.
available at: http://nettoe.sourceforge.net
Now, I'd really like to see it in the Debian
distribution so I'm just trying to understand
how I can make it possible.
I have jus
On Tue, May 01, 2001 at 10:33:39PM +1000, Drew Parsons wrote:
> Thanks for your responses, all :)
>
> Setting the file permissions properly seems to be the main need for the root
> build environment.
A lot of packages used to test for root access in the clean target too.
That was standard practi
On Thu, May 03, 2001 at 08:23:19AM +1000, Hamish Moffatt wrote:
> A lot of packages used to test for root access in the clean target too.
> That was standard practise before we had fakeroot.
>
> I suppose when you were building as root (non-fake), you would end up
> with directories owned by root
> Now, I'd really like to see it in the Debian
> distribution so I'm just trying to understand
> how I can make it possible.
Do you want to become a debian developer or do you want someone else to
maintain the package?
If you're interested in being a dd, you should apply. Follow the
instruction
i'd like to package the opengl manpages... but there tarballs are a bit
strange... they're .Z files to begin with, and they don't appear to have
a version number (some other docs have 1.2 as a version, so i suppose i
can assume this) and the files untar into a directory called
"release". I'm guess
> i'd like to package the opengl manpages... but there tarballs are a bit
> strange... they're .Z files to begin with, and they don't appear to have
> a version number (some other docs have 1.2 as a version, so i suppose i
> can assume this) and the files untar into a directory called
> "release".
20 matches
Mail list logo
