Neil Schemenauer <[EMAIL PROTECTED]> writes:
> I'm on vacation until Oct. 17 but I should have experimental packages
> ready soon after that, they are almost done already. I don't know
> what's happening with Woody. Can anyone explain it to me? Gregor seems
> to be busy with other things righ
Anthony Towns wrote:
> Which scheme was that?
Quickly:
python-2.1_2.1.1
python_2.1.1 (depends on python-2.1) (does "ln /usr/bin/python{2.1,}")
python-2.1-_ (depends on python-2.1)
python-_ (depends on python and python-2.1-)
_ (depends on python and python-,
#!/u
On Wed, Oct 10, 2001 at 10:28:58AM -0700, Neil Schemenauer wrote:
> Anthony Towns wrote:
> > Hrm. That doesn't seem to make sense. For example, Python 2.1 supports
> > the Python 2.0 API completely, and Python 2.2 supports the Python 2.1
> > API completely too, doesn't it?
> API in this context mea
> The point is probably moot anyhow since I've almost finished creating
> packages using the scheme proposed by Donavon and others. I need to
> update the policy and doing some more testing yet though.
That's good news. I'm itching to try out some of the new features. Would I
be able to assist in
Anthony Towns wrote:
> Hrm. That doesn't seem to make sense. For example, Python 2.1 supports
> the Python 2.0 API completely, and Python 2.2 supports the Python 2.1
> API completely too, doesn't it?
API in this context means binary API. Only Python 2.1.X supports the
2.1 API.
The point is proba
On Sun, Sep 30, 2001 at 01:52:00PM -0700, Neil Schemenauer wrote:
> Donovan Baarda wrote:
> > Hmmm, but if only "python" can provide python-api-*, then any packages that
> > depend on python-api-X.Y will be broken when a new version of python
> > providing python-api-X.Z comes out, and no python-X.
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Donovan Baarda wrote:
> > Hmmm, but if only "python" can provide python-api-*, then any packages
> that
> > depend on python-api-X.Y will be broken when a new version of python
> > providing python-api-X.Z comes out, and no python-X.Y package can be
Donovan Baarda wrote:
> Hmmm, but if only "python" can provide python-api-*, then any packages that
> depend on python-api-X.Y will be broken when a new version of python
> providing python-api-X.Z comes out, and no python-X.Y package can be
> compatible with it.
That's right. Packaged modules mu
On Sat, Sep 29, 2001 at 11:31:44PM -0700, Neil Schemenauer wrote:
> Packages (mostly) conforming to this policy are at:
[...]
> - Packaged modules should depend on python-api-X.Y
>
> - Remove section on legacy versions of Python (they are
> independent). I should probably add a sect
Packages (mostly) conforming to this policy are at:
deb http://people.debian.org/~nas woody/
I've updated a lot of packages. If there is something missing that you
use please let me know. After updating about 30 packages I'm getting
good at it. :-)
Changes from last version (off the top o
10 matches
Mail list logo
