Bugzilla Bug 30119

Hi,
this is a preliminary ebuild for the new y window system, a x window system
replacement:
http://www.doc.ic.ac.uk/~mbt99/Y/

This release won't build without a patch: my patch is attached and used within
the ebuild, new versions will be alvaible at http://tina.polito.it/~axa/stuff/
until the upstream author won't restart working on the project.

Paolo

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Created an attachment (id=18582) [details]
y-base/y/y-0.1.ebuild

depends on libiterm-mbt (bug report sent: 30117)

Created an attachment (id=18583) [details]
patch needed to build y

Official Y-0.1 doesn't build, I made this patch to fix it.

http://tina.polito.it/~axa/stuff/ for updates

*** Bug 42285 has been marked as a duplicate of this bug. ***

Just as a note... I've been maintaining support for this @
http://www.cardoe.com/y-base/

Ebuilds and extra patches and all. They're used by the Y developers & hackers.

You can pull my e-builds from the site.

I've deleted some of the older versioned ebuilds so only Y-0.2_pre4 through
Y-0.2_p11 are available.

Notice the versioning... we use Arch to develop Y. So basically a random patch
in the Y--devel--0.2 patchset was declared Y-0.2 release. (in fact it was
Y--devel--0.2--patch-10) so all the patches prior to patch-10 are _pre# and the
ones after are _p# until we decide we're gonna start on the Y-0.3 version.

You should rename y to y-windows because emerge search y is nearly impossible
;)

That's what regular expressions are for. =)
emerge -s ^y$

If you try the ebuilds off my site (which are actually updated to the latest
version). They're called y-base/y-windows.

I am no longer maintaining the original ebuild and I'm using Doug Goldstein's
ones instead.
I hope they will be soon added to gentoo.

Doug, great work! I am happy to see that Y is active again; I've been waiting
for it to resume for a while. I like the name change, y-windows is more
descriptive and easier to find.

I'll have more time later tonight to test the ebuilds, and hopefully commit
them.

Thanks!

Hallgrimur, despite the name y-windows, please don't create a new category
y-base with only a few packages in it. Put it in x11-base for now.

Okay, I've committed y-windows. I made a few changes:

Added two dependencies: >=autoconf-2.58 >=automake-1.8
Moved from category y-base to x11-base.
Renamed Changelog to ChangeLog.
Added Gentoo to copyright notice.
Added metadata.xml.
Changed ./configure to econf and removed all parameters; they are already set in
 econf.

Btw, "aclocal -I automake" from autogen.sh gives alot of warnings when WANT_AUT
OMAKE="1.8" is set.

I haven't committed pylibY yet, I'll have to talk to the python herd first about putting it in dev-python/.

Thanks again.

Hallgrimur, maybe you failed to notice the whole copyright assignment deal a
while ago, but you shouldn't have committed this dual-copyrighted ebuild. If
Doug Goldstein won't assign his copyright to Gentoo, you need to pull this from
the tree.

Oh, sorry, my mistake. I haven't had a dual copyright ebuild before, so I
haven't followed the discussion too closely; I thought drobbins recommended
dual copyrights, but his position has apparently changed.

Doug, read up on http://www.gentoo.org/proj/en/devrel/copyright-assignment.xml

Will you assign the copyright to gentoo?

The former opinion was his before talking to his lawyer, I believe. =)

this pack should be in p.mask given it's alpha status.

Why does it use a patched source from a different location than the y homepage? In my opinion ebuilds always should use the official sources as a starting point.

automake & autoconf are clear buildtime only deps.

Don't set a long description in metadata if it's not long, it doesn't add anything  like this. In the same sense the description in the ebuild itself is also duplication, if i want the name i can just get it from the ebuild name or the dir it is in. Descriptions should be descriptive.

Sure Gentoo can have the copyright.

As far as downloading from an alternate source, the main Y webpage doesn't have tar'd up packages. There is an outdated version on their site. Currently the author recommends using GNU Arch to pull the latest version and then installing from that, or at least tar'ing that up to make the release tarball. And that's all the tarball is, no patched sources.

Someone should change the Summary of this bug... It contains a typo and it
should be renamed to y-windows ...

close? 0.2 is already in portage?

Comment #15 clearly indicates some remaining issues.

I agree with foser; I think we should use the official version from the Y
homepage, even if it's outdated - that's rather an issue for the Y developers
to fix.

Currently, 0.2 is the latest official release. Y-patch26, which is currently in
portage, fixes some bugs in 0.2 release, so for the time being I'll continue
using that, but when the 0.3 is released I'll start using that instead.

How can I emerge y-windows without installing Xfree as well

My USE flags are:
-X -gtk -gnome -qt -kde -alsa

and it still tries to compile Xfree

In portage, closing.