-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 - e
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 mutu
On Wed, 2008-04-16 at 07:34 +0100, Ciaran McCreesh wrote:
> 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, the
Michael Haubenwallner wrote:
On Wed, 2008-04-16 at 07:34 +0100, Ciaran McCreesh wrote:
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 manage
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 implement
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
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 implement
Since my blog doesn't get syndicated on planet.gentoo.org I'm posting the
entry here again, but it's probably a good idea anyway:
First I want to apologize for the current situation. I know we're lagging
behind and I know that bugs are piling up.
As a small excuse I can only say that my time is li
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
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 oft
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.
Bl
"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
On 09:55 Wed 16 Apr , Tiziano Müller wrote:
> What do the new ebuilds offer:
> a) A split into dev-db/postgresql-{base,server,docs}. Now, I know that
> splitting up packages isn't the Gentoo way. I know we could have done it
> using USE flags but this approach gives more flexibility due to the
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 Andres
On Wed, 16 Apr 2008 10:40:49 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> I don't know if it would be feasible from a package manager point of
> view, but couldn't some (most?) blockers be avoided if there was some
> means to transfer ownership of installed files from one package to
> another?
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 and with sending error. Maybe switch like
"--force-install"?
> On Wed, 16 Apr 2008, Ciaran McCreesh wrote:
> Blocks do not work:
> * It's often not obvious what the user's supposed to do to resolve a
> block.
> * Once the user has worked out how to resolve the block correctly,
> it's often hard to do so since resolving some blocks is best done by
> fo
Donnie Berkholz wrote:
> On 09:55 Wed 16 Apr , Tiziano Müller wrote:
>> What do the new ebuilds offer:
>> a) A split into dev-db/postgresql-{base,server,docs}. Now, I know that
>> splitting up packages isn't the Gentoo way. I know we could have done it
>> using USE flags but this approach give
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
signatur
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
Desc
Jeroen Roovers wrote:
Dear ebuild maintainers,
thirty days is the norm for the minimal period between an ebuilds last
non-keywording change while in the tree and the usual call for
stabilisation. If you cannot find a pressing reason to push
stabilisation forward, then don't ask. In the las
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 because
"Mateusz A. Mierzwin'ski" <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Wed, 16 Apr 2008 09:52:13
+0200:
> Yes... and then all trashes like old libs are inside system.
Long since solved problem. emerge --depclean
> Other thing
> is when some files gets from one package to
"Mateusz A. Mierzwiński" <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Wed, 16 Apr 2008 10:18:37
+0200:
> 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 re
Duncan pisze:
"Mateusz A. Mierzwiński" <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Wed, 16 Apr 2008 10:18:37
+0200:
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 wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Mateusz A. Mierzwiński,
I really appreciate your trying to help, but your command of the English
language is such
that I and others have a lot of trouble making sense out of what you write.
Perhaps you
should consider that you also have probl
Vlastimil Babka wrote:
Jeroen Roovers wrote:
On the other hand, maybe these early stabilisation bug reports are a
sign of the times and we need to shorten the normal thirty day period,
become even more of a cutting edge distro - or at least discuss the
options.
I'd say leave the current norm a
> c) Upgrading between major versions of PostgreSQL requires the DB admin to
> bump the database using the old version, moving the database away and to
> reload the dump into a new database cluster using the new version of
> PostgreSQL. Having to take down the old server and purging the old version
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 wrong - I also have that
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
Carsten Lohrke wrote:
>> c) Upgrading between major versions of PostgreSQL requires the DB admin
>> to bump the database using the old version, moving the database away and
>> to reload the dump into a new database cluster using the new version of
>> PostgreSQL. Having to take down the old server
Marijn Schouten (hkBst) pisze:
Hello Mateusz A. MierzwiDski,
I really appreciate your trying to help, but your command of the
English language is such
that I and others have a lot of trouble making sense out of what you
write. Perhaps you
should consider that you also have problems understandi
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'
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 w
On Wed, 16 Apr 2008 19:17:51 +0200
Frank Gruellich <[EMAIL PROTECTED]> wrote:
> I was not able to create a filename or path containing it. (Anyone
> else?)
Unix file names can't contain / or null.
> Unfortunately that stupid sed does not work with \x00 as
> delimiter...
Nor do most Unix apps, s
* Marius Mauch <[EMAIL PROTECTED]> 15. Apr 08:
> On Tue, 15 Apr 2008 16:17:54 +0200
> Frank Gruellich <[EMAIL PROTECTED]> wrote:
> > * Santiago M. Mola <[EMAIL PROTECTED]> 15. Apr 08:
> > > On Tue, Apr 15, 2008 at 1:14 PM, Marijn Schouten (hkBst)
> > > Currently is use ':' as sed delimiter when pat
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
runnin
On Wed, 2008-04-16 at 11:49 +0200, Vlastimil Babka wrote:
> > thirty days is the norm for the minimal period between an ebuilds last
It is the norm. It is not a requirement. In fact, it is specifically a
"guideline" rather than a hard rule. It is up to the maintainer's
discretion when to ask fo
Wed, 16 Apr 2008 12:09:24 -0700
Chris Gianelloni <[EMAIL PROTECTED]> kirjoitti:
> On Wed, 2008-04-16 at 11:49 +0200, Vlastimil Babka wrote:
> > > thirty days is the norm for the minimal period between an ebuilds
> > > last
>
> It is the norm. It is not a requirement. In fact, it is
> specifical
On Wed, 16 Apr 2008 18:59:26 +0200
"Mateusz A. Mierzwiński" <[EMAIL PROTECTED]> wrote:
> I just want to know that Gentoo will be usable for me and my client's
> that I provide Gentoo Linux support. I recommending Gentoo whatever I
> can, but when I see what happens than I starting to worry.
If
Ciaran McCreesh <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Wed, 16 Apr 2008
18:24:05 +0100:
> On Wed, 16 Apr 2008 19:17:51 +0200
> Frank Gruellich <[EMAIL PROTECTED]> wrote:
>> I was not able to create a filename or path containing it. (Anyone
>> else?)
>
> Unix file name
Duncan a écrit :
Whatever your faults, you /do/
tend to be quite accurate on such things.
Wow, you've managed to turn a nice technical discussion (which is rare
enough in recent history) into a let's-start-bashing-people thread.
You've lost all credibility in just one sentence... Pity.
If i
43 matches
Mail list logo
