Remi Mommsen wrote:
[]
on. You are asking for an interactive mode for creating package files...
In addition it violates the fink policy that a deb file with a given
name/version/revision should be identical regardless how and where it
was built.
It violates the even more important principle
Sure, we can wait.
If there are bugs in 0.18.0 which need to be addressed, then we should fix
them both in CVS HEAD, and in branch_0_18, and plan to release 0.18.1
which addresses them. Then, after 0.18.1 has been tested for a while,
we can move it to stable and only then release 0.19.0.
--
Just install a more recent man (fink's one for example) and it will
display localised man pages, following your environment settings.
Worked for me with fink's man 1.5k.
I've found no fink's man, sorry, just manconf which is for Jaguar
update and manedit, a graphical editor.
Saw that.
Am 04.02.2004 um 02:53 schrieb Ben Hines:
[...]
I believe this is not our fault. SF's SQL server is simply hosed
today. This has happened in the past, nothing unusual.
Indeed, all other projects are affected, too. SF.net staff is looking
into it - seems some project is doing something improper
I'm happy to release 0.18.1 with this bugfix. Any other bugs that we need
to squash in the same release?
-- Dave
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What version of dpkg? I forgot to make dselect understand the virtual
packages until a slightly later revision of dpkg. I believe this user will
find that both apt-get and dpkg work fine, only dselect is broken.
Peter
Martin Costabel wrote:
| I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Barker wrote:
|From /sw/bin/dpkg-name, there is a line that says version=1.10.9
|
Sorry, 'dpkg -l dpkg' should tell you the installed version-revision, the
revision is the important field in this case. I should ahve said that in my
last message.
I'm really talking about two things, one of which is no problem.
1. being able to change compile time options
No problem, its already possible. Everyone agrees that you better
know roughly what you're doing, or the package won't work.
2. being able to dynamically find satisfy dependencies
Joe Corneli wrote:
I'm really talking about two things, one of which is no problem.
1. being able to change compile time options
No problem, its already possible. Everyone agrees that you better
know roughly what you're doing, or the package won't work.
2. being able to dynamically find
Actually I've been meaning to do up a document on this, for the benefit
of users who want to muck around with their compile-time options. The
day job keeps interfering, though.
--
Alexander Hansen
Levitated Dipole Experiment
http://www.psfc.mit.edu/LDX
On Feb 4, 2004, at 3:08 PM, Joe Corneli
10 matches
Mail list logo
