Enrico Weigelt wrote:
* Ciaran McCreesh [EMAIL PROTECTED] schrieb:
Hi,
Hi Enrico, long time no see!
b) Marking that two related implementations are mutually incompatible at
runtime because they both provide the same binary.
Classical example: MTA's:
Traditionally they tend to provide an
Wednesday, 16 of April 2008 11:07:20 Mateusz A. Mierzwiński wrote:
Markus Rothe pisze:
Mateusz A. Mierzwiński wrote:
Yes, You have right but I have thinking about something like OPTION for
emerge or switch to enable that function. Emerge could provide two
options of working - with replace
* Donnie Berkholz [EMAIL PROTECTED] schrieb:
A slight tweak that you may have already considered: a single package is
split into multiple packages with a metabuild (named the same as the
original single package) in a newer version -- for example, modularized
X.
hmm, let's just thing
Enrico Weigelt wrote:
* Ciaran McCreesh [EMAIL PROTECTED] schrieb:
Hi,
Hi Enrico, long time no see!
b) Marking that two related implementations are mutually incompatible at
runtime because they both provide the same binary.
Classical example: MTA's:
Traditionally they tend to provide an
Enrico Weigelt wrote:
* Bernd Steinhauser [EMAIL PROTECTED] schrieb:
Hi,
e) A package needs a newer version of another package, but doesn't depend
on it.
This was the case with KDE4. kdelibs-4.0.x block these packages:
!kde-base/kdebase-3.5.7-r6
!kde-base/kdebase-startkde-3.5.7-r1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| On Wed, 16 Apr 2008 07:54:48 +0200
| Mateusz A. Mierzwin'ski [EMAIL PROTECTED] wrote:
| And I strongly suggest to leave old mechanism of portage, because we
| saw couple times what _GREAT_ automatic makes with distro - eg.
|
On 06:24 Wed 16 Apr , Ciaran McCreesh wrote:
What all are blocks used for?
a) Marking that two unrelated packages are mutually incompatible at
runtime because they happen to collide, for example on a commonly named
executable.
b) Marking that two related implementations are mutually
On Wed, 2008-04-16 at 07:34 +0100, Ciaran McCreesh wrote:
snip
Case D, Current Behaviour: User tries to upgrade coreutils. User gets a
big flashy block error saying coreutils blocks mktemp. User doesn't
realise that the safe upgrade path is to force the package manager to
ignore the block,
Michael Haubenwallner wrote:
On Wed, 2008-04-16 at 07:34 +0100, Ciaran McCreesh wrote:
snip
Case D, Current Behaviour: User tries to upgrade coreutils. User gets a
big flashy block error saying coreutils blocks mktemp. User doesn't
realise that the safe upgrade path is to force the package
Donnie Berkholz pisze:
On 06:24 Wed 16 Apr , Ciaran McCreesh wrote:
What all are blocks used for?
a) Marking that two unrelated packages are mutually incompatible at
runtime because they happen to collide, for example on a commonly named
executable.
b) Marking that two related
On Wed, 16 Apr 2008 09:52:13 +0200
Mateusz A. Mierzwin'ski [EMAIL PROTECTED] wrote:
Yes... and then all trashes like old libs are inside system. Other
thing is when some files gets from one package to other. If You
install old version of package A and then some of files get to
package A1 as an
Donnie Berkholz pisze:
On 06:24 Wed 16 Apr , Ciaran McCreesh wrote:
What all are blocks used for?
a) Marking that two unrelated packages are mutually incompatible at
runtime because they happen to collide, for example on a commonly named
executable.
b) Marking that two related
On Wednesday 16 April 2008 09:56:04 Mateusz A. Mierzwiński wrote:
My Prof from US used to say - if something is working good why we should
replace it? When we do that we can be sent to the tree with bananas
straighting proposition by OS.
I think it has been made quite clear in this thread that
On Wed, 16 Apr 2008 09:56:04 +0200
Mateusz A. Mierzwiński [EMAIL PROTECTED] wrote:
My Prof from US used to say - if something is working good why we
should replace it? When we do that we can be sent to the tree with
bananas straighting proposition by OS.
Blocks do not work:
* It's often not
Bo Ørsted Andresen pisze:
On Wednesday 16 April 2008 09:56:04 Mateusz A. Mierzwiński wrote:
My Prof from US used to say - if something is working good why we should
replace it? When we do that we can be sent to the tree with bananas
straighting proposition by OS.
I think it has been
Ciaran McCreesh pisze:
On Wed, 16 Apr 2008 09:56:04 +0200
Mateusz A. Mierzwiński [EMAIL PROTECTED] wrote:
My Prof from US used to say - if something is working good why we
should replace it? When we do that we can be sent to the tree with
bananas straighting proposition by OS.
Blocks
Mateusz A. Mierzwiński wrote:
Yes, You have right but I have thinking about something like OPTION for
emerge or switch to enable that function. Emerge could provide two options
of working - with replace and with sending error. Maybe switch like
--force-install?
This is not a thread about a
On Wednesday 16 April 2008 10:15:16 Mateusz A. Mierzwiński wrote:
So why not to send on screen info about what to do rather then ERROR?
Please reread this entire thread. That's exactly what is being proposed.
[...]
I think this is good idea.
I think this is a terrible idea.
--
Bo Andresen
On Wednesday, 16. April 2008 11:03:29 Ciaran McCreesh wrote:
I think that this thread is about making Gentoo unstable, unusable
and user non-friendly.
I think you really don't have the slightest clue what this thread is
about.
Don't feed the trolls...
--
Best regards, Wulf
signature.asc
On Wed, 16 Apr 2008 11:07:20 +0200
Mateusz A. Mierzwiński [EMAIL PROTECTED] wrote:
I think that this thread is about making Gentoo unstable, unusable
and user non-friendly.
I think you really don't have the slightest clue what this thread is
about.
--
Ciaran McCreesh
signature.asc
Ciaran McCreesh schrieb:
What all are blocks used for?
a) Marking that two unrelated packages are mutually incompatible at
runtime because they happen to collide, for example on a commonly named
executable.
b) Marking that two related implementations are mutually incompatible at
runtime
Bo Ørsted Andresen wrote:
On Wednesday 16 April 2008 10:15:16 Mateusz A. Mierzwiński wrote:
So why not to send on screen info about what to do rather then ERROR?
Please reread this entire thread. That's exactly what is being proposed.
I'd go one step further. Don't tell the user what to
Richard Freeman pisze:
Bo Ørsted Andresen wrote:
On Wednesday 16 April 2008 10:15:16 Mateusz A. Mierzwiński wrote:
So why not to send on screen info about what to do rather then ERROR?
Please reread this entire thread. That's exactly what is being proposed.
I'd go one step further. Don't
Richard Freeman pisze:
Mateusz A. Mierzwin'ski wrote:
And I strongly suggest to leave old mechanism of portage, because we
saw couple times what _GREAT_ automatic makes with distro - eg.
Mandriva with all creators and cheap installer - couple apps not
running, low performance.
Don't get me
Mateusz A. Mierzwin'ski kirjoitti:
Richard Freeman pisze:
Mateusz A. Mierzwin'ski wrote:
And I strongly suggest to leave old mechanism of portage, because we
saw couple times what _GREAT_ automatic makes with distro - eg.
Mandriva with all creators and cheap installer - couple apps not
25 matches
Mail list logo
