ow if
someone added something, so you do it all over again each time. A zip
file is scanned only once.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t to depend on it using setuptools). In the case of
other frameworks -- including TurboGears (which I think is the ultimate
packaging goal here) -- the Egg metadata really is important, it's not
just used for dependencies.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbi
here's a 1-to-1 mapping from packages to
eggs/projects, but that covers many situations, especially cases where
we're currently seeing conflicts. You lose the ability to easily
support multiple versions of a package with this, though that could
probably be handled too.
--
Ian Bicking /
you do for TurboGears
would be installed as eggs, but packages already available won't be
installed as eggs.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ts (e.g., MySQLdb) installed as
Debian packages. I'd rather not step on the toes of installed packages,
but I also want a development environment that tracks the projects I
care about. Maybe you are just saying that Debian packages are
unsuitable for software development. Maybe that is true;
ds to be taken into account. Much of the software we are currently
talking about is primarily targeted at people like myself (the exception
would be Trac, though even that has a developer focus). This may change
at some point -- there might be useful applications that Debian users
want easy access t
Josselin Mouette wrote:
Le dimanche 27 novembre 2005 à 16:26 -0600, Ian Bicking a écrit :
No one is forcing Debian to package any of these.
Of course you are forcing Debian to package these. As long as your
projects have enough users, someone will want to build a Debian package.
The whole
7 matches
Mail list logo
