Mailing List Archive

On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
> Do I simply mail a
> patch to this list, or ask somebody for a CVS account and commit
> changes directly?

Bugzilla: bugs.gentoo.org


> I'm also a bit confused about the portdir_overlay thing - If there
> exists a -r15, do I then add a -r16 to make emerge realize an
> update is available. What happens then when an -r16 hits the
> regular portage tree?

Nothing at all. If there's a conflict between the standard tree and your
overlay, the ebuild in the overlay takes priority.


--
Anthony Gorecki
Ectro-Linux Foundation

Casey Allen Shobe wrote:

>I'm planning to edit the vpopmail ebuild Real Soon Now to add the
>mysteriously missing postgres USE flag and thus end up with a
>package compiled with the support we need.
>
>Instead of wasting my time re-adding this every time a new version
>of vpopmail comes along, I'd much rather use this as an opportunity
>to get into Gentoo development and add this to the central ebuild
>repository so that all future versions inherit it.
>
>What do I need to do to get started on this? Do I simply mail a
>patch to this list, or ask somebody for a CVS account and commit
>changes directly?
>
>
>
You should file a bug in http://bugs.gentoo.org.

>I'm also a bit confused about the portdir_overlay thing - If there
>exists a -r15, do I then add a -r16 to make emerge realize an
>update is available. What happens then when an -r16 hits the
>regular portage tree?
>
>
if r15 exists in portdir_overlay, it will be preferred over the official
r15 version.

On Sun, 2005-07-17 at 22:07 -0700, Anthony Gorecki wrote:
> On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
> > I'm also a bit confused about the portdir_overlay thing - If there
> > exists a -r15, do I then add a -r16 to make emerge realize an
> > update is available. What happens then when an -r16 hits the
> > regular portage tree?
>
> Nothing at all. If there's a conflict between the standard tree and your
> overlay, the ebuild in the overlay takes priority.

In other words, something very important: You miss all the potentially
critical changes contained in the new "official" revision.

Thanks,
Donnie

On Sunday, July 17, 2005 11:57 pm, Donnie Berkholz wrote:
> In other words, something very important: You miss all the potentially
> critical changes contained in the new "official" revision.

Yes, that's an important, /minor/ issue that I neglected to mention.

At the time, I assumed that he would be aware of the risk, without thinking
that he may not have been entirely familiar with the packaging system. In
retrospect, it would have been helpful to mention that using an overlay
without care can render a system unusable with alacrity :)


--
Anthony Gorecki
Ectro-Linux Foundation

maillog: 17/07/2005-23:57:05(-0700): Donnie Berkholz types
> On Sun, 2005-07-17 at 22:07 -0700, Anthony Gorecki wrote:
> > On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
> > > I'm also a bit confused about the portdir_overlay thing - If there
> > > exists a -r15, do I then add a -r16 to make emerge realize an
> > > update is available. What happens then when an -r16 hits the
> > > regular portage tree?
> >
> > Nothing at all. If there's a conflict between the standard tree and your
> > overlay, the ebuild in the overlay takes priority.
>
> In other words, something very important: You miss all the potentially
> critical changes contained in the new "official" revision.

Since that's a common issue, maybe portage could warn the user sort of
like this:

$ emerge -pv app-foo/bar
...
Warning: app-foo/bar-0.1-r2: [1] overrides a newer ebuild in [0]
[ebuild R] app-foo/bar-0.1-r2 0kB [1]
Portage overlays:
[0] /usr/portage
[1] /usr/portage-local

I know [0] exists in my head only, but that's for illustration only.

"newer" in this case refers to the mtime of the two ebuilds. The user
checks, merges changes (or simply touches the ebuild in their overlay)
and the warning goes away.

However, there is also the possibility to lose all the critical changes
from your overlay if you accidentally install the "official" newer
revision (I bet there are plenty of people who may forget a package that
they have in their overlays). That's already covered by
http://bugs.gentoo.org/show_bug.cgi?id=67072 though.


--
*) Georgi Georgiev *) Department chairmen never die, they just *)
(* chutz@gg3.net (* lose their faculties. (*
*) +81(90)2877-8845 *) *)

On Mon, 2005-07-18 at 04:26 +0000, Casey Allen Shobe wrote:
> What do I need to do to get started on this? Do I simply mail a
> patch to this list, or ask somebody for a CVS account and commit
> changes directly?

Well, becoming a developer requires some time. If you're simply looking
to submit this one ebuild, then file a bug on bugs.gentoo.org and attach
the ebuild to it.

> I'm also a bit confused about the portdir_overlay thing - If there
> exists a -r15, do I then add a -r16 to make emerge realize an
> update is available. What happens then when an -r16 hits the
> regular portage tree?

Nothing would happen. Since you would already have -r16 installed,
portage would just skip it. Once -r17 hit the tree, it would be
upgraded to the in-tree version.

--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

On Monday 18 July 2005 06:57, Donnie Berkholz wrote:
> On Sun, 2005-07-17 at 22:07 -0700, Anthony Gorecki wrote:
> > On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
> > > I'm also a bit confused about the portdir_overlay thing - If
> > > there exists a -r15, do I then add a -r16 to make emerge
> > > realize an update is available. What happens then when an
> > > -r16 hits the regular portage tree?
> >
> > Nothing at all. If there's a conflict between the standard tree
> > and your overlay, the ebuild in the overlay takes priority.
>
> In other words, something very important: You miss all the
> potentially critical changes contained in the new "official"
> revision.

So if I read correctly, when using an overlay, just don't change the
version number - a rebuild will be sufficient to use the overlay
version. Righto.

Cheers,
--
Casey Allen Shobe | http://casey.shobe.info
cshobe@seattleserver.com | cell 425-443-4653
AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523
SeattleServer.com, Inc. | http://www.seattleserver.com
--
gentoo-dev@gentoo.org mailing list

On Monday 18 July 2005 13:19, Chris Gianelloni wrote:
> If you're simply looking to submit this one ebuild, then file a
> bug on bugs.gentoo.org and attach the ebuild to it.

I'm sure there will be more - there are a number of ebuilds I have
small issues with that I just workaround. I'm much more inclined
to just fix the problem instead of complaining about it because of
past experiences involving reporting hundreds of bugs, many of
which are not fixed to this day 2 years later.

Cheers,
--
Casey Allen Shobe | http://casey.shobe.info
cshobe@seattleserver.com | cell 425-443-4653
AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523
SeattleServer.com, Inc. | http://www.seattleserver.com
--
gentoo-dev@gentoo.org mailing list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Casey Allen Shobe wrote:
> I'm sure there will be more - there are a number of ebuilds I have
> small issues with that I just workaround. I'm much more inclined
> to just fix the problem instead of complaining about it because of
> past experiences involving reporting hundreds of bugs, many of
> which are not fixed to this day 2 years later.


if you have the same problem with multiple packages or multiple problems with
the same package, usually filing a metabug is a good idea

- --

smithj

Gentoo Developer
[ desktop stuff && network monitoring && documentation ]


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC2/SSl5AvwDPiUowRAq3EAJ4qSm9k4jxNCl9ypNgTsGi4UluSvgCfeJjU
Ct5vS1wR5ERrhbxMfu4rb7k=
=Hl5j
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list

On Mon, 2005-07-18 at 18:19 +0000, Casey Allen Shobe wrote:
> On Monday 18 July 2005 13:19, Chris Gianelloni wrote:
> > If you're simply looking to submit this one ebuild, then file a
> > bug on bugs.gentoo.org and attach the ebuild to it.
>
> I'm sure there will be more - there are a number of ebuilds I have
> small issues with that I just workaround. I'm much more inclined
> to just fix the problem instead of complaining about it because of
> past experiences involving reporting hundreds of bugs, many of
> which are not fixed to this day 2 years later.

Sounds like you'd be a candidate for the QA team. Perhaps you should
get in touch with both them and the recruiters.

--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

Casey Allen Shobe posted <200507181813.28298.lists@seattleserver.com>,
excerpted below, on Mon, 18 Jul 2005 18:13:28 +0000:

> On Monday 18 July 2005 06:57, Donnie Berkholz wrote:
>> On Sun, 2005-07-17 at 22:07 -0700, Anthony Gorecki wrote:
>> > On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
>> > > I'm also a bit confused about the portdir_overlay thing - If there
>> > > exists a -r15, do I then add a -r16 to make emerge realize an update
>> > > is available. What happens then when an -r16 hits the regular
>> > > portage tree?
>> >
>> > Nothing at all. If there's a conflict between the standard tree and
>> > your overlay, the ebuild in the overlay takes priority.
>>
>> In other words, something very important: You miss all the potentially
>> critical changes contained in the new "official" revision.
>
> So if I read correctly, when using an overlay, just don't change the
> version number - a rebuild will be sufficient to use the overlay version.
> Righto.

Exactly. The overlay is used first, if a copy exists there.

Of course, you'll need to re-digest the changed version, and anything in
FILESDIR it uses will need to be moved to the overlay FILESDIR, or an
attempted merge of the package with an overlay copy existing will fail,
(IOW, it will prefer the overlay copy and fail if the digest doesn't
match, even if a digest matching copy exists in the main portage tree),
but that should follow from the above.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


--
gentoo-dev@gentoo.org mailing list