Philipp Kern wrote:
On Thu, 2005-07-14 at 23:24 -0400, kamaraju kusumanchi wrote:
After compiling it, I will get two libraries (runtime and development
libraries). I named these packages as libfortranposix0,
libfortranposix0-dev according to their soname.
It's libfortranposix0 for
Hi,
After compiling it, I will get two libraries (runtime and development
libraries). I named these packages as libfortranposix0,
libfortranposix0-dev according to their soname.
It's libfortranposix0 for the runtime library and libfortranposix-dev
for the development package. (If you
Like Alex, I think if one program has problem, we need to solve this
problem against upstream author. Because he know his program and know
how to solve bugs, etc.
I too think like Bartosz Fenski, but with one difference.
if you're going to package something written in Python it is
Oleksandr Moskalenko wrote:
Having a good relationship with upstream helps immensely especially if the
maintainer doesn't know C or C++ or whatever the software is written in. Maybe
that should be in the policy, too ;)
We really should not take it to the absurd extremes.
That is true, but
On Fri, 15 Jul 2005 01:20:44 +0200, Bartosz Fenski aka fEnIo [EMAIL
PROTECTED] said:
On Fri, Jul 15, 2005 at 12:10:50AM +0100, Roger Leigh wrote:
If you can't understand what you are packaging, you shouldn't be
packaging it, IMHO.
So maybe our documentation should state that?
Err,
On 14/07/05, Jose Carlos do Nascimento [EMAIL PROTECTED] wrote:
Hi, All
I'm mantainer of zoo package and I need help to solve this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309594
Have you considered looking at how gzip, zip, unzip, tar, ... handle
this stuff? You may be able to
On 15-Jul-2005, Manoj Srivastava wrote:
Bartosz Fenski aka fEnIo [EMAIL PROTECTED] said:
On Fri, Jul 15, 2005 at 12:10:50AM +0100, Roger Leigh wrote:
If you can't understand what you are packaging, you shouldn't be
packaging it, IMHO.
So maybe our documentation should state that?
Err,
Could be because it's actually called SNEeSe.
http://sourceforge.net/projects/sneese/
Cheers,
- Michael
(Follow-ups to debian-legal, please.)
FWIW, I would not touch SNEeSe or any fragment derived from it with a
ten-foot pole unless they can tell you where sneese.dat came from and
what's in it. My guess is that it is an infringing copy of the
contents of an SNES64 ROM and that the history of its
On Fri, 2005-07-15 at 06:53 -0700, Richard A. Hecker wrote:
That is true, but we do have an obligation to our users. Every DD makes
mistakes. What is the
chance they might upload something that contains a Trojan if they do not
know the source? How
would they be able to check a claim if
On 7/15/05, skaller [EMAIL PROTECTED] wrote:
Oh .. which DD can be responsible for my package Felix then?
They would have to know:
* C/C++
* OCaml
* Python
* Bash
* Interscript
* Felix
* ocamllex/ocamlyacc and Elkhound
* HTML/XML
* Latex/troff/texinfo
* snippets of 10 other
Penis Enlargement Patch That Works!!!
http://www.xunepa.com/ss/
Laughter is the closest distance between two people.
Laughter is the first evidence of freedom.
Death hath so many doors to let out life.
Everything that can be invented has been invented.
The rest is
On Fri, 2005-07-15 at 19:23 -0700, Michael K. Edwards wrote:
On 7/15/05, skaller [EMAIL PROTECTED] wrote:
Oh .. which DD can be responsible for my package Felix then?
They would have to know:
* C/C++
* OCaml
* Python
* Bash
* Interscript
* Felix
* ocamllex/ocamlyacc and
13 matches
Mail list logo
