Summary: | adesklets-0.1.0.ebuild (New package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | S.Fourmanoit <syfou> |
Component: | New packages | Assignee: | Gentoo Dockapp Team <desktop-dock> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | bert, gad.kadosh |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 84940, 85980 | ||
Bug Blocks: | |||
Attachments: |
ebuild for adesklets-0.1.0
Ebuild for adesklets 0.1.1 adesklets 0.3.0 ebuild adesklets 0.3.1 ebuild |
Description
S.Fourmanoit
2005-01-29 01:24:29 UTC
Created attachment 49804 [details]
ebuild for adesklets-0.1.0
Created attachment 49998 [details]
Ebuild for adesklets 0.1.1
This is an updated version of previous ebuild for adesklets 0.1.1
- It fixes a directory mismatch that caused html doc to be installed in subdirs
of
'html/'.
- It adds post install warning messages for users that choosed unusual USE
flags
combinations.
Please consider this instead of adesklets-0.1.0.ebuild the up-to-date ebuild
ready for inclusion in portage.
I get this error while trying to "digest" the ebuild ebuild adesklets-0.1.1.ebuild digest !!! aux_get(): ebuild path for 'local/adesklets-0.1.1' not specified: !!! None !!! aux_get(): ebuild path for 'local/adesklets-0.1.1' not specified: !!! None doebuild(): aux_get() error reading local/adesklets-0.1.1; aborting Ooops! I may have jumped the gun here...I put the ebuild in the wrong directory which caused me to not be able to digest. It is resolved on my end. Everything worked fine. So sorry adesklets 0.1.2 is out! You may know rename previously submitted adesklets.0.1.1.ebuild to adesklets-0.1.2.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. adesklets 0.1.4 is out! You may know rename previously submitted adesklets.0.1.1.ebuild to adesklets-0.1.4.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. Sorry for the typo. adesklets 0.1.3 is out, not adesklets 0.1.4... ignore the previous comment. You may know rename previously submitted adesklets.0.1.1.ebuild to adesklets-0.1.3.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. adesklets 0.2.0 is out! You may know rename previously submitted adesklets.0.1.1.ebuild to adesklets-0.1.4.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. adesklets 0.2.1 is out! You may know rename previously submitted adesklets.0.1.1.ebuild to adesklets-0.2.1.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. Please also note release 0.2.0 was broken for gentoo systems using GNU readline<5.0 . This release (0.2.0) should be totally forgotten, as 0.2.1 supersets it, since it is a mere bug fix to this specific problem. May I ask what the rationale is for putting the X use flag in the ebuild? If I understand this correctly this program needs X to work properly, so being able to build it without X seems like defeating it's purpose...? > May I ask what the rationale is for putting the X use flag in the ebuild?
In fact, if you intend using it for displaying desklets, you are perfectly right, X should be optional. However, if want you want is a command line graphic editor (on a headless server, for instance) that give you a way to alter dynamically an image, as gd or imagemagick could, you do not absolutely need X, and adesklets was also written with such a use in mind (see the install page from the doc).
Now, I acknowledge this to be strange for an package suggested to be placed in portage inside the x11-plugins category... This is why I put a big warning is post-install, but I am very opened to better way for handling this.
Sorry for the grammatical error in last comment. You should read, of course: In fact, if you intend using it for displaying desklets, you are perfectly right, X should NOT be optional [...] Created attachment 51028 [details]
adesklets 0.3.0 ebuild
New ebuild for adesklets 0.3.0. Added support for installation of texinfo
manuals.
Please considfer this ebuild the one ready for inclusion in portage.
Created attachment 51191 [details]
adesklets 0.3.1 ebuild
New ebuild for adesklets 0.3.1. Upgraded python requirements.
Please considfer this ebuild the one ready for inclusion in portage.
adesklets 0.3.2 is out! You may know rename previously submitted adesklets.0.3.1.ebuild to adesklets-0.3.2.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. adesklets 0.4.0 is out! You may now rename previously submitted adesklets.0.3.1.ebuild to adesklets-0.4.0.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. Hello Gentoo Dockapp Team, this bug report is now almost a month old. This is not a flame, as I know you are certainly busy some place else... Nevertheless, I would appreciate your feedback on this (the bug has not even been assigned yet - maybe it is this normal for submitted ebuilds though, I am not familiar with bugzilla) - I am quite ready to change the ebuild as needed, but I first need your comments! adesklets is already working well for a growing number of gentoo users, including me. From the forums: http://forums.gentoo.org/search.php?show_results=topics&search_terms=all&search_keywords=adesklets It has already been included without any effort from myself in a number of others source distributions, such as archlinux, fnux, and even many well-known Mandrake's urpmi medias. Someone from slackware contacted me about it, and freebsd 'Ports and Packages Collection' are also considering inclusion. It begins to feel weird not having an ebuild out of the box for gentoo, my main development system. :-) Hope to hear from you soon, adesklets 0.4.1 is out! You may now rename previously submitted adesklets.0.3.1.ebuild to adesklets-0.4.1.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. adesklets 0.4.2 is out! You may now rename previously submitted adesklets.0.3.1.ebuild to adesklets-0.4.2.ebuild without any other change. Please note that the adesklets-0.4.1 package was broken for all python 2.3.x users, so it should just be thrown away, as this one is merely a bug correction release. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. thanks for the ebuild. hopefully it'll get picked up soon. i've seen these things sit for years before. adesklets 0.4.3 is out! You may now rename previously submitted adesklets.0.3.1.ebuild to adesklets-0.4.3.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. adesklets 0.4.4 is out! You may now rename previously submitted adesklets.0.3.1.ebuild to adesklets-0.4.4.ebuild without any other change. Please consider this newly renamed ebuild the up-to-date ebuild ready for inclusion in portage. OK, adeskets is now in Portage, under x11-misc/adesklets. Thank you for the ebuild work (and constant reminders)! Hi Michele Noberasco, I noticed the included ebuild in portage have only ~x86 in keywords... Just to tell you I also tested the program on gentoo amd64, and I have another developper doing all its work on an Itanium (on FC3, though); but I guess it is better to start things this way. Thanks for the inclusion! I can confirm that adesklets builds great on ~amd64, ever since 0.1.0. :-) OK, I added the ~amd64 keyword to the ebuild. Cannot add the ~ia64 one unless it is tested on gentoo with the provided ebuild. Also, for the future, you should post info about new versions as separate bugs. And requests for additional archs, too, as they should be handled by the appropriate arch teams, not by me. |