README in rst
This commit is contained in:
parent
ff14477f60
commit
e17e0de19a
@ -1,7 +1,7 @@
|
|||||||
include AUTHORS
|
include AUTHORS
|
||||||
include COPYING
|
include COPYING
|
||||||
include NEWS
|
include NEWS
|
||||||
include README
|
include README.rst
|
||||||
include TODO
|
include TODO
|
||||||
include setup.py
|
include setup.py
|
||||||
recursive-include bin *
|
recursive-include bin *
|
||||||
|
@ -5,12 +5,12 @@ dev-portage/euscan
|
|||||||
------------------
|
------------------
|
||||||
|
|
||||||
euscan is available in portage as a dev package (app-portage/euscan-9999).
|
euscan is available in portage as a dev package (app-portage/euscan-9999).
|
||||||
This tool allow to check if a given package/ebuild has new upstream versions
|
This tool allows to check if a given package/ebuild has new upstream versions
|
||||||
or not. It will use different heuristic to scan upstream and grab new versions
|
or not. It will use different heuristic to scan upstream and grab new versions
|
||||||
and related urls.
|
and related urls.
|
||||||
|
|
||||||
This tool was designed to mimic debian's uscan, but there is a major
|
This tool was designed to mimic debian's uscan, but there is a major
|
||||||
difference between the two: uscan uses a specific "watch" file that describe
|
difference between the two: uscan uses a specific "watch" file that describes
|
||||||
how it should scan packages, while euscan uses only what can already be found
|
how it should scan packages, while euscan uses only what can already be found
|
||||||
in ebuilds. Of course, we could later add some informations in metadata.xml
|
in ebuilds. Of course, we could later add some informations in metadata.xml
|
||||||
to help euscan do its job more efficiently.
|
to help euscan do its job more efficiently.
|
||||||
@ -242,4 +242,3 @@ This one uses rubygems's json API
|
|||||||
### Pypy
|
### Pypy
|
||||||
|
|
||||||
Uses pypy's XML rpc API.
|
Uses pypy's XML rpc API.
|
||||||
|
|
@ -1,23 +0,0 @@
|
|||||||
"""
|
|
||||||
This file demonstrates two different styles of tests (one doctest and one
|
|
||||||
unittest). These will both pass when you run "manage.py test".
|
|
||||||
|
|
||||||
Replace these with more appropriate tests for your application.
|
|
||||||
"""
|
|
||||||
|
|
||||||
from django.test import TestCase
|
|
||||||
|
|
||||||
|
|
||||||
class SimpleTest(TestCase):
|
|
||||||
def test_basic_addition(self):
|
|
||||||
"""
|
|
||||||
Tests that 1 + 1 always equals 2.
|
|
||||||
"""
|
|
||||||
self.failUnlessEqual(1 + 1, 2)
|
|
||||||
|
|
||||||
__test__ = {"doctest": """
|
|
||||||
Another way to test that 1 + 1 is equal to 2.
|
|
||||||
|
|
||||||
>>> 1 + 1 == 2
|
|
||||||
True
|
|
||||||
"""}
|
|
@ -21,4 +21,4 @@ if settings.DEBUG:
|
|||||||
url(r'^static/(?P<path>.*)$', 'django.views.static.serve', {
|
url(r'^static/(?P<path>.*)$', 'django.views.static.serve', {
|
||||||
'document_root': os.path.join(settings.EUSCAN_ROOT, 'htdocs'),
|
'document_root': os.path.join(settings.EUSCAN_ROOT, 'htdocs'),
|
||||||
}),
|
}),
|
||||||
)
|
)
|
||||||
|
Loading…
Reference in New Issue
Block a user