[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Renaming wm/enlightenment to wm/enlightenment16
"David H. Gutteridge" <david%gutteridge.ca@localhost> writes:
> I'd like to rename wm/enlightenment to wm/enlightenment16, and
> wm/ethemes to wm/ethemes16, to distinguish them from x11/enlightenment.
> The former represents the "E16" branch of Enlightenment, which
> continues to be maintained separately upstream (and which I'd like to
> keep in pkgsrc, since it has a smaller footprint than its successors).
> wm/enlightenment and x11/enlightenment should be able to co-exist
> in the same installtion, if desired. I'll also reverify this. (Oh, and
> wm/ethemes only works with the "E16" branch. The theme format
> changed in incompatible ways with "E17".)
> I don't imagine there would be any objections, but I know renaming
> packages isn't done lightly, so I thought I'd ask.
That seems sensible. There is a pretty strong notion that when there
are multiple versions that each PKGPATH should be versioned, and that we
should not undo this for a long time, even if we end up with only one
after a while. Basically being slow to rename, and the notion that any
package that needed two versions before may need two versions again,
because it's a clue about upstream practices.
In this case, I think this is a fork, not two versions from an upstream,
and your 16 label on the fork seems likely to give the right
I would expect that x11/enlightenment would be simply updated to 18.x
when/if that is released, and there would be no need to keep 17 around.
Main Index |
Thread Index |