Ability to delete packages?

[mvantellingen]

Ability to delete packages?

[mvantellingen]

Yeah I agree. This needs to be implemented. Will take a look at it asap

[dbrgn]

Yes please :) As a workaround, is it enough to remove the package in the admin?

[lovato]

Just look out what I described on issue #61. If you remove it, nobody can guarantee that someone already downloaded it, and worse: if you upload a different package (different source code) with same version. We will have inconsistency.

[dbrgn]

The same problem exists on the "real" pypi too, though. It's just something that you shouldn't do.

Removing packages during the testing phase would be great though. It's the users responsibility not to delete packages that other people are already using (similar to force-rewriting public VCS repositories).

[llonchj]

Latest development branch contains a menu to access Django admin.

[lovato]

I have a PROD and DSV localshops. Probaly there can be a switch to enable or not that. Will not remove packages on my production environment. Just increment version, fix it and submit it again. Perhaps the best is to mark the package as bad_package. So no one will be able to download it again. And also never overide it.

[llonchj]

I can see your point having 2 localshop instances. As localshop acts also as a pypi proxy, have you considered using only one localshop and specify the version to download in setup.py or requirements.txt?

[lovato]

The DSV one is intended for testing only. Package creation/upload tests. If the package is well configured, tested and so on, it goes to production.

[lovato]

DSV version was discontinued :-)

[llonchj]

Marco,

What are the reasons to discontinue DSV version? Are you now installing
version-specific modules of your products?

Cheers,
Jordi

2013/9/5 Marco Lovato [email protected]

DSV version was discontinued :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/36#issuecomment-23793219
.

[lovato]

No, no.
We had 2 localshops, one for testing our packaging process, and other one
for real packages.
Since we kind of mastered the packaging, and found the django /admin path,
we no longer need the DSV version.
It was the very same localshop version installed on both.

Marco

[]s

Lovato

sent from GMail

On Wed, Sep 4, 2013 at 2:07 PM, Jordi Llonch [email protected]:

Marco,

What are the reasons to discontinue DSV version? Are you now installing
version-specific modules of your products?

Cheers,
Jordi

2013/9/5 Marco Lovato [email protected]

DSV version was discontinued :-)

—
Reply to this email directly or view it on GitHub<
https://github.com/mvantellingen/localshop/issues/36#issuecomment-23793219>

.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/36#issuecomment-23806427
.

[llonchj]

Thanks @lovato. I am about to implement CI for the whole devel process in a platform. This is why I was curious about your process.