-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
aowdDBQFEEAQnW5ql+IAeqTIRAlkd6AJsGQ82Bn79PukWYEdsVsBRFeAzAowCgmRdN
WauYdVaZFXVlBRP/M5l+SmQ=
=VcTX
-END PGP SIGNATURE-
Guys honestly why aren't we as developers doing a massive overhaul on dpkg?
I feel we are running on pre
Okay, I posted to -devel a few weeks back with a proposal for an update to dpkg.
This message is being Cc'd to -devel, and sent to -dpkg.
Basically, attached is my proposal (it's long, I'm trimming it down in another
rxvt, but, I wanted to get something out for the firing sqaud). Please read it
On Sat, Mar 11, 2006 at 12:06:40PM -0800, John Gee wrote:
> Guys honestly why aren't we as developers doing a massive overhaul on dpkg?
> I feel we are running on pre-historic machines here. There needs to be at
> least a little looking toward the future in our blood.
What exactly are you missi
On Sat, Mar 11, 2006 at 09:31:29PM +0100, Michael Koch wrote:
> On Sat, Mar 11, 2006 at 12:06:40PM -0800, John Gee wrote:
> > Guys honestly why aren't we as developers doing a massive overhaul on dpkg?
> > I feel we are running on pre-historic machines here. There needs to be at
> > least a litt
fantumn Steven Baker" wrote:
> have this little g (imlib and fnlib come to mind). Since libc5 exists for the
> most part only in the hearts of the Slackware users, this 'g' thing can be
> dropped.
No it can't. Please consider backwards compatability.
> Another problem with this is that many pa
Hi,
>>"fantumn" == fantumn \(Steven Baker\) writes:
What is wrong with cvs-buildpackage? I maintain all my
packages in CVS, and there is a well defined version based
tagging scheme.
What exactly are you attempting to solve here that has not
already been solved?
fantumn> C
Manoj Srivastava wrote:
> What exactly are you attempting to solve here that has not
> already been solved?
He's trying to solve the fact that we have package names like "libgtk1.1.11"
and "slang0.99.38".
> Why do CVS based packages need a special name? I am missing
> something here
On Wed, Jan 20, 1999 at 04:03:26PM -0500, fantumn Steven Baker" wrote:
> Package Naming Scheme
The problem is superficial. Sure, names should be more uniform, but all
this requires is 1) ratifying naming standards and 2) ensuring that the
packaging system handles name changes gracefully.
> CVS
On Wed, 20 Jan 1999, Andrew Pimlott wrote:
<...>
Hmmm, would the concept of meta-packages and a scheme for sharing common
files (like the RH one described?) work.
Packages could have their name extended with the version:
foo_1.2.3-1 -> foo_1.2.3
foo_1.2.3-2 -> foo_1.2.3
foo_1.2.4-1 -> foo_1.2.4
First of all: please use a standard textwidth of at most 76. Right now
your mail frankly looks horrible. Only due to vim's awesome reformating
power is sending a reply doable :)
Previously fantumn Steven Baker" wrote:
> Package Naming Scheme
> ---
> The current naming scheme o
On Wed, Jan 20, 1999 at 11:36:00PM -0500, Andrew Pimlott wrote:
> On Wed, Jan 20, 1999 at 04:03:26PM -0500, fantumn Steven Baker" wrote:
> > Package Naming Scheme
>
> The problem is superficial. Sure, names should be more uniform, but all
> this requires is 1) ratifying naming standards and 2) en
Wichert Akkerman wrote:
> case) incompatible? This is where RH and Debian seem to differ: for RH
> they become the same package, and you need multiple versions of the same
> package to support all applications. This is probably why they need
> hacks like dependencies on files to get this working.
Craig Sanders wrote:
> i agree. in fact, it's more like a solution searching for a problem than
> even a superficial problem.
It's a problem that is only evident to people who haven't lived with it for
years. That doesn't mean it's not a problem.
> from the descriptions that have been posted of h
On Fri, Jan 22, 1999 at 12:02:55AM -0800, Joey Hess wrote:
> Craig Sanders wrote:
> > i agree. in fact, it's more like a solution searching for a problem than
> > even a superficial problem.
>
> It's a problem that is only evident to people who haven't lived with it for
> years. That doesn't mean
On Fri, 22 Jan 1999, Craig Sanders wrote:
> the libgtk* versions are compatible with each other. the libgtk*-dev
> versions, are not (it would be possible to make it so by installing
> header files in /usr/include/gtk-VERSION, but you'd still have to modify
> every source file that #included it. in
Craig Sanders wrote:
> 300 sounds like a lot...are you including all shared libs and -dev and
> -altdev packages?
No, I was just including everything that ended with a number. That excludes
the -dev packages and it probably includes some things that don't belong. As
I said, it's a "crude" count.
On Fri, Jan 22, 1999 at 02:05:26PM -0800, Joey Hess wrote:
> > in any case, i don't see it as a problem. IMO, the fact that they have
> > different package names is USEFUL information. it tells me that there's
> > something possibly weird or dangerous going on and i should be extra
> > careful be
As I said before, rpm does have the capability to install 2 different
versions of a package simulantaneously. Here's how it works, to the best of
my knowledge.
User interface:
Rpm differentiates between installing a package and upgrading a package.
Installing a package (rpm -i) simply unpacks th
On Wed, Jan 20, 1999 at 03:42:15PM -0800, Joey Hess wrote:
|
|So rpm's method of upgrading is the same as dpkg -i, whereas dpkg has nothing
|equivilant to rpm's method of just installing a package.
|
|Oh and by the way, this user interface tends to confuse new users (at least
|it did me) who accid
Anthony Wong wrote:
> |Oh and by the way, this user interface tends to confuse new users (at least
> |it did me) who accidentially install many versions of the same package
> |because they arn't aware they should be upgrading it instead.
>
> Because you already have the Debian way in your mind whe
Hi!
> Joey Hess writes:
JH> What happens if you try to install version bar of a package while
JH> version foo of that same package, which contains files of the
JH> same name, is installed? Rpm will happily overwrite version foo's
JH> files.
Yes.
JH> What happens if you then remove vers
Joey Hess <[EMAIL PROTECTED]> writes:
> As I said before, rpm does have the capability to install 2 different
> versions of a package simulantaneously. Here's how it works, to the best of
> my knowledge.
> User interface:
> Rpm differentiates between installing a package and upgrading a package.
Package: dpkg
Version: 1.0.6
1. Missing documentation:
No man pages for dpkg, update-rc.d, and update-alternatives.
2. dpkg/update-alternatives doesn't give me the level of installation
control I expected. If one wants to install each of elvis/nvi/vim (each
of which provides vi), dpkg
| Guillem Jover <[EMAIL PROTECTED]>:
| reassign 363486 debian-policy
|
| each package should agree on which interface is needed to be able to
| provide a specific alternative. And if they should provide a virtual
| package for it.
|
| On Wed, 2006-04-19 at 14:44:08 +0300, Jari Aalto wrote:
| > Pa
On 6/12/06, Jari Aalto <[EMAIL PROTECTED]> wrote:
Is there any coordinated effort to standardize the name of the provided
programs in /etc/alternatives?
I don't think this concerns debian-policy at all. The use of
alternatives is something that needs to be coordinated amont the
maintainers of
an off-topic question:
why x-office-word, x-office-excel, etc?
are these trying to express "the replacement for microsoft windows
word, excel" ?
or is this what text documents or spreadsheet documents being called?
-- Fred
On 6/12/06, Margarita Manterola <[EMAIL PROTECTED]> wrote:
On 6/12/06,
| an off-topic question:
|
| why x-office-word, x-office-excel, etc?
| are these trying to express "the replacement for microsoft windows
| word, excel" ?
| or is this what text documents or spreadsheet documents being called?
It's almost industry standard to refer to "Word" as the word processor
On Mon, Jun 12, 2006 at 12:53:57PM +0300, Jari Aalto wrote:
> | >
> | > The same problem is with Office programs:
> | >
> | > lyx
> | > abiword
> | > oowriter
> | > ...
> | >
> | > The /etc/alternatives contains a good framework to canonicalize actions to
> | > common names available in
On 6/12/06, Kurt Roeckx <[EMAIL PROTECTED]> wrote:
I'm not sure if the alternatives system is the best place to
"register" mime types. I'm also not sure that a Debian specific
solution as the alternatives system is the best way to go. But I
can see why this would be useful, and maybe it should
Le lundi 12 juin 2006 à 20:44 +0200, Kurt Roeckx a écrit :
> I think you're not very clear in what you're asking, so I'm going
> to try and explain what I think you said.
>
> If you open a file in a file browser, or you open it thru a web
> browser or something, it might have a mime type assosiate
* Tue 2006-06-13 Josselin Mouette
* Message-Id: 1150231486.17236.21.camel AT utena.localnet
> Le lundi 12 juin 2006 à 20:44 +0200, Kurt Roeckx a écrit :
>
>> I think you're not very clear in what you're asking, so I'm going
>> to try and explain what I think you said.
>>
>> If you open a file in
Am Mittwoch, 14. Juni 2006 00:53 schrieb Jari Aalto+mail.linux:
> * Tue 2006-06-13 Josselin Mouette
> * Message-Id: 1150231486.17236.21.camel AT utena.localnet
>
> > Le lundi 12 juin 2006 à 20:44 +0200, Kurt Roeckx a écrit :
> >> I think you're not very clear in what you're asking, so I'm going
>
* Wed 2006-06-14 Hendrik Sattler
>>
>> The proposal here talks about differnt thing, but indirectly concerns
>> the mime types, which are used to associate actions to certain file
>> extensions.
>
> Why not have something that starts the proper program according to the given
> mimetype? E.g.:
> x
Le mercredi 14 juin 2006 à 01:33 +0200, Hendrik Sattler a écrit :
> > >> If you open a file in a file browser, or you open it thru a web
> > >> browser or something, it might have a mime type assosiated with
> > >> it. So what I think you suggest is that based on the mime-type
> > >> we start an a
On Wed, Jun 14, 2006 at 01:53:29AM +0300, Jari Aalto+mail.linux wrote:
> Command line usage (or from Window manager menu):
>
> call: x-spreadsheet
How would this be different from using the already-existing run-mailcap
command? And what happens if 95% of time I want to use one application
as
* Wed 2006-06-14 Thibaut Paumard
* Message-Id: 1150288566.1225.141.camel AT pc-paumard.mpe-garching.mpg.de
> Le mercredi 14 juin 2006 à 01:33 +0200, Hendrik Sattler a écrit :
>
>> Why not have something that starts the proper program according to the given
>> mimetype? E.g.:
>> x-mime-handler app
On 6/14/06, Jari Aalto+usenet <[EMAIL PROTECTED]> wrote:
One thing, when etc/mailcap entry reads:
application/msexcel; oocalc '%s'; edit=oocalc '%s
What happens then 'oocalc' is not available? How is
the error handling done, so that e.g. 'xmessage' is
displayed under Window mamager to notify
On Wed, 2006-06-14 at 03:06:09 +0300, Jari Aalto+mail.linux wrote:
> I don't see real obstacle here. Granted that the alternatives system
> should be extended to look for
>
> $HOME/debian/alternatives
>
> Before checking
>
> /etc/laternatives
>
> Perhaps I should file a wishlist for it.
Your message dated Mon, 8 Sep 2008 17:43:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line implemented elsewhere already (or please file seperate bugs if
thats not enough)
has caused the Debian Bug report #363486,
regarding dpkg: [update-alternatives] New categories for: WORD,
39 matches
Mail list logo