On Sat, Jun 10, 2000 at 10:21:39PM -0500, Aaron Malone wrote:
> can do "grep-available python|grep ^Package|awk '{print $2}'|wc -l"
oops. Lose the "|wc -l" from that, I pasted from a terminal and
forgot to remove it. :)
--
Aaron Malone ([EMAIL PROTECTED])
System Administrator "
On Sat, Jun 10, 2000 at 10:38:07PM +0200, Tomasz Wegrzanowski wrote:
>
> What about RE-searching for ^py ???
"grep-available python" is useful as well. To get a list of all the
packages that have "python" in the requirements or descriptions, you
can do "grep-available python|grep ^Package|awk '{
On Fri, Jun 09, 2000 at 02:44:36PM +0200, JИrТme Marant wrote:
> > I am pretty sure that python- prefix is for packages that provide some
> > functionality
> > in /usr/lib/site-python, /usr/lib/python{version}/site-packages
>
> Do you mean those whose .py files directly fit in site-packages itsel
On Sat, Jun 10, 2000 at 11:56:46AM -0600, Bruce Sass wrote:
> On 10 Jun 2000, Andreas Voegele wrote:
> > >> In my opinion, packages like "pygtk" and "pyqt" that add new
> > >> modules to Python should always be renamed to "python-*" [...]
> >
> > > [...]
> >
> > > As far as findin
On 10 Jun 2000, Andreas Voegele wrote:
> >> In my opinion, packages like "pygtk" and "pyqt" that add new
> >> modules to Python should always be renamed to "python-*" [...]
>
> > [...]
>
> > As far as finding stuff in dselect goes... try "/".
>
> That is what I'm doing. But dsele
>> In my opinion, packages like "pygtk" and "pyqt" that add new
>> modules to Python should always be renamed to "python-*" [...]
> [...]
> As far as finding stuff in dselect goes... try "/".
That is what I'm doing. But dselect does only support simple substring
searches and whe
On Jun 09, Michael Sobolev wrote:
> On Fri, Jun 09, 2000 at 11:16:13AM +0200, Jérôme Marant wrote:
> > Do all Debian python packages have to be prefixed by 'python-' ?
> > I recently packaged the "pyunit" software and I still don't
> > know if I have to rename it python-unit or if I can keep its
>
On 9 Jun 2000, Andreas Voegele wrote:
> someone wrote:
> > I would rather not go for renaming upstream packages, to avoid
> > confusion.
>
> In my opinion, packages like "pygtk" and "pyqt" that add new modules
> to Python should always be renamed to "python-*" since it is much
> easier to
Radovan Garabik <[EMAIL PROTECTED]> writes:
> I am not a priori against, but there has to be a limit somewhere, and I guess
> this is a borderline case.
Again, to my mind, it is a practical reason: it would be better to know
that htmlgen is a set of python classes, what you cannot guess as
the p
On Fri, Jun 09, 2000 at 06:04:57PM +0200, Jérôme Marant wrote:
> Radovan Garabik <[EMAIL PROTECTED]> writes:
>
> > there are however some issues...
> > I have packaged pyncurses (http://pyncurses.sourceforge.net), which is
> > a new, object oriented interface for ncurses.
> > I cannot rename it t
Radovan Garabik <[EMAIL PROTECTED]> writes:
> there are however some issues...
> I have packaged pyncurses (http://pyncurses.sourceforge.net), which is
> a new, object oriented interface for ncurses.
> I cannot rename it to python-ncurses, since that is an upstream
> name of another program (and
On Fri, Jun 09, 2000 at 04:50:53PM +0200, Jérôme Marant wrote:
> Andreas Voegele <[EMAIL PROTECTED]> writes:
>
> > In my opinion, packages like "pygtk" and "pyqt" that add new modules
> > to Python should always be renamed to "python-*" since it is much
> > easier to find these packages with dsel
Andreas Voegele <[EMAIL PROTECTED]> writes:
> In my opinion, packages like "pygtk" and "pyqt" that add new modules
> to Python should always be renamed to "python-*" since it is much
> easier to find these packages with dselect if a consistent naming
> scheme is used.
I would say "all python lib
> I would rather not go for renaming upstream packages, to avoid
> confusion.
In my opinion, packages like "pygtk" and "pyqt" that add new modules
to Python should always be renamed to "python-*" since it is much
easier to find these packages with dselect if a consistent naming
scheme is
Radovan Garabik <[EMAIL PROTECTED]> writes:
> If you are writting a package _for_ python, such as python-mpz, it is
> appropriate if mpz is a standalone library, otherwise aesthetic
> criteria apply :-)
In my case, pyunit is a python library and is a standalone library, so
I think it would be
On Fri, Jun 09, 2000 at 11:16:13AM +0200, Jérôme Marant wrote:
>
> Hi,
>
> Do all Debian python packages have to be prefixed by 'python-' ?
that is probably not necessary, compare with packages written in perl
(latex2html came to my mind immediately)
If you are writting a package _for_ python,
Michael Sobolev <[EMAIL PROTECTED]> writes:
> Looks like there is at least one package that does not follow this "policy":
> reportbug. Hmm, zope also uses its own naming scheme... :)
>
> I am pretty sure that python- prefix is for packages that provide some
> functionality
> in /usr/lib/site
On Fri, Jun 09, 2000 at 11:16:13AM +0200, JИrТme Marant wrote:
> Do all Debian python packages have to be prefixed by 'python-' ?
> I recently packaged the "pyunit" software and I still don't
> know if I have to rename it python-unit or if I can keep its
> name as is.
Looks like there is at least o
18 matches
Mail list logo
