* [gentoo-portage-dev] two remarks on portage-2.0.51-r2
@ 2004-10-23 12:17 Pablo De Napoli
2004-10-23 12:30 ` Roman Gaufman
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Pablo De Napoli @ 2004-10-23 12:17 UTC (permalink / raw
To: gentoo-portage-dev
I see that portage-2.0.51-r2 is now stable.
However, It has some useful features that are deprecated or broken.
1) emerge --upgradeonly
Why is this deprecated? I think it is endeed a useful feature.
I'm not sure that the files /etc/portage/package* are a good (esay-to-use)
replacement for it.
2) emerge ebuild by path
Acording to the man page, this is broken, however it is the most obvious way
to specify an ebuild, isn't it?
Why is this feature broken, could anybody find out?
I think is very important to keep the quality of portage to the highest standards, so I
suggest not to realese as stable a version with important features broken.
Best regards
Pablo De Napoli
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
--
gentoo-portage-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2
2004-10-23 12:17 [gentoo-portage-dev] two remarks on portage-2.0.51-r2 Pablo De Napoli
@ 2004-10-23 12:30 ` Roman Gaufman
2004-10-23 12:36 ` Roman Gaufman
2004-10-23 13:18 ` Marius Mauch
2004-10-23 13:50 ` Jason Stubbs
2 siblings, 1 reply; 6+ messages in thread
From: Roman Gaufman @ 2004-10-23 12:30 UTC (permalink / raw
To: gentoo-portage-dev
1) If you dont know how to echo package-name
>>/etc/portage/package.keywords you shouldnt even bother with masked
or hard masked packages.
2) Emerging path-to-ebuild doesnt append package to the world file,
thus breaking emerge depclean and emerge -up world. --- Very bad idea
and over long term can seriously break system concistency.
To maintain the concistency of your system, allowing you to have a
system as clean as when you installed years after, these 2 things
should be avoided at all cost, and thus deprecated and warned highly
against.
On Sat, 23 Oct 2004 05:17:15 -0700 (PDT), Pablo De Napoli
<pdenapo@yahoo.com> wrote:
> I see that portage-2.0.51-r2 is now stable.
> However, It has some useful features that are deprecated or broken.
>
> 1) emerge --upgradeonly
>
> Why is this deprecated? I think it is endeed a useful feature.
> I'm not sure that the files /etc/portage/package* are a good (esay-to-use)
> replacement for it.
>
> 2) emerge ebuild by path
>
> Acording to the man page, this is broken, however it is the most obvious way
> to specify an ebuild, isn't it?
>
> Why is this feature broken, could anybody find out?
>
> I think is very important to keep the quality of portage to the highest standards, so I
> suggest not to realese as stable a version with important features broken.
>
> Best regards
>
> Pablo De Napoli
>
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
>
> --
> gentoo-portage-dev@gentoo.org mailing list
>
>
--
gentoo-portage-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2
2004-10-23 12:30 ` Roman Gaufman
@ 2004-10-23 12:36 ` Roman Gaufman
0 siblings, 0 replies; 6+ messages in thread
From: Roman Gaufman @ 2004-10-23 12:36 UTC (permalink / raw
To: gentoo-portage-dev
Oh, just to clarify. Using emerge path-to-ebuild always had those side
effects and was only intended for developer usage to begin with!
It isnt something new in .51 -- its just finally a warning was put.
On Sat, 23 Oct 2004 12:30:45 +0000, Roman Gaufman <hackeron@gmail.com> wrote:
> 1) If you dont know how to echo package-name
> >>/etc/portage/package.keywords you shouldnt even bother with masked
> or hard masked packages.
>
> 2) Emerging path-to-ebuild doesnt append package to the world file,
> thus breaking emerge depclean and emerge -up world. --- Very bad idea
> and over long term can seriously break system concistency.
>
> To maintain the concistency of your system, allowing you to have a
> system as clean as when you installed years after, these 2 things
> should be avoided at all cost, and thus deprecated and warned highly
> against.
>
>
>
>
> On Sat, 23 Oct 2004 05:17:15 -0700 (PDT), Pablo De Napoli
> <pdenapo@yahoo.com> wrote:
> > I see that portage-2.0.51-r2 is now stable.
> > However, It has some useful features that are deprecated or broken.
> >
> > 1) emerge --upgradeonly
> >
> > Why is this deprecated? I think it is endeed a useful feature.
> > I'm not sure that the files /etc/portage/package* are a good (esay-to-use)
> > replacement for it.
> >
> > 2) emerge ebuild by path
> >
> > Acording to the man page, this is broken, however it is the most obvious way
> > to specify an ebuild, isn't it?
> >
> > Why is this feature broken, could anybody find out?
> >
> > I think is very important to keep the quality of portage to the highest standards, so I
> > suggest not to realese as stable a version with important features broken.
> >
> > Best regards
> >
> > Pablo De Napoli
> >
> >
> > _______________________________
> > Do you Yahoo!?
> > Declare Yourself - Register online to vote today!
> > http://vote.yahoo.com
> >
> > --
> > gentoo-portage-dev@gentoo.org mailing list
> >
> >
>
--
gentoo-portage-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2
2004-10-23 12:17 [gentoo-portage-dev] two remarks on portage-2.0.51-r2 Pablo De Napoli
2004-10-23 12:30 ` Roman Gaufman
@ 2004-10-23 13:18 ` Marius Mauch
2004-10-23 13:50 ` Jason Stubbs
2 siblings, 0 replies; 6+ messages in thread
From: Marius Mauch @ 2004-10-23 13:18 UTC (permalink / raw
To: gentoo-portage-dev
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 10/23/04 Pablo De Napoli wrote:
> 2) emerge ebuild by path
>
> Acording to the man page, this is broken, however it is the most
> obvious way to specify an ebuild, isn't it?
>
> Why is this feature broken, could anybody find out?
It never really worked. It did a lookup from the given filename in the
portage tree and converted the filename to a cpv entry (as most portage
functions only deal with cpv entries and not full filenames). This means
that in some situations portage used a different ebuild than you
specified.
It also had several side effects that aren't documented and caused bogus
bugreports.
> I think is very important to keep the quality of portage to the
> highest standards, so I suggest not to realese as stable a version
> with important features broken.
To keep the quality we added those warnings. These features (I don't
consider them important) were always broken, to fix them we'd have to
re-implement them completely and make several API changes.
Marius
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2
2004-10-23 12:17 [gentoo-portage-dev] two remarks on portage-2.0.51-r2 Pablo De Napoli
2004-10-23 12:30 ` Roman Gaufman
2004-10-23 13:18 ` Marius Mauch
@ 2004-10-23 13:50 ` Jason Stubbs
2004-10-23 18:33 ` Pablo De Napoli
2 siblings, 1 reply; 6+ messages in thread
From: Jason Stubbs @ 2004-10-23 13:50 UTC (permalink / raw
To: gentoo-portage-dev
On Saturday 23 October 2004 21:17, Pablo De Napoli wrote:
> I see that portage-2.0.51-r2 is now stable.
> However, It has some useful features that are deprecated or broken.
>
> 1) emerge --upgradeonly
>
> Why is this deprecated? I think it is endeed a useful feature.
> I'm not sure that the files /etc/portage/package* are a good (esay-to-use)
> replacement for it.
Downgrades happen when:
* a package's versioning changes and it is actually an upgrade,
* a package is broken and dangerous, or
* masking has been bypassed in some way.
In the first two cases, you want the change to happen. In the
third, /etc/portage/package* serves you much better.
> 2) emerge ebuild by path
>
> Acording to the man page, this is broken, however it is the most obvious
> way to specify an ebuild, isn't it?
>
> Why is this feature broken, could anybody find out?
It was always broken. It is fact now slightly less broken than it was in
2.0.50. At least now it'll prevent tell you when you are going to install
something unmasked - which is it's main use by developers - and actually
cancel the merge when it's not about to merge that which you asked for.
> I think is very important to keep the quality of portage to the highest
> standards, so I suggest not to realese as stable a version with important
> features broken.
No offense but I find this almost comical. Have a look on bugs.g.o for portage
bugs. You'd be surprised I think. 2.0.51 has bugs - even a couple of new ones
that should be fixed soon - but there's nothing really broken that wasn't
broken before.
Regards,
Jason Stubbs
--
gentoo-portage-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2
2004-10-23 13:50 ` Jason Stubbs
@ 2004-10-23 18:33 ` Pablo De Napoli
0 siblings, 0 replies; 6+ messages in thread
From: Pablo De Napoli @ 2004-10-23 18:33 UTC (permalink / raw
To: gentoo-portage-dev
Thannk you every one for your explanations, in fact I don't know well the portage
internals (even though I want to follow the portage development and help with ideas)
I didn't mean to offend anybody, I apologise if I did it somehow.
Best regards.
Pablo De Napoli
> No offense but I find this almost comical. Have a look on bugs.g.o for portage
> bugs. You'd be surprised I think. 2.0.51 has bugs - even a couple of new ones
> that should be fixed soon - but there's nothing really broken that wasn't
> broken before.
>
> Regards,
> Jason Stubbs
>
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
--
gentoo-portage-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-10-23 18:33 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-23 12:17 [gentoo-portage-dev] two remarks on portage-2.0.51-r2 Pablo De Napoli
2004-10-23 12:30 ` Roman Gaufman
2004-10-23 12:36 ` Roman Gaufman
2004-10-23 13:18 ` Marius Mauch
2004-10-23 13:50 ` Jason Stubbs
2004-10-23 18:33 ` Pablo De Napoli
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox