Wocka 0.5 - checkinstall for Arch Linux

mxcl · 2006-07-04 10:40:07

sud_crow wrote:

I did a wocka --makepkg (as i wanted to keep the pkg around for distribution), and it built the package ok, but when i installed it, i found it was installed to /usr/local/bin, instead of the usual Arch style of /usr/bin.
I think you should review the part where it runs the configure script to include the flag --prefix=/usr

Actually, I'm not sure about this as, for instance, kde packages will by default detect the kde prefix and install there. Installing some KDE packages to non KDE prefixes breaks the packages. So on Arch /usr is not /opt/kde.

Perhaps I can read the makefile and determine if the package will be installed to /usr/local and modify the generated build files. This would only work for auto* but that would do. A lot of work though, so wouldn't be in the next version as I'm still working on broader issues.

lumiwa · 2006-07-07 23:11:25

mxcl wrote:

With Wocka you can do:
./configure
make
su
wocka
and you'll get the application installed, and a pacman db entry too.
Wocka automatically figures out the package name, version and/or
Comments, contributions, etc. most welcome! Thanks.
..........

Thanks for your very helpful program . For me as so far for computers education is VERY helpful...

sud_crow · 2006-07-07 23:45:20

mxcl wrote:

sud_crow wrote:
I did a wocka --makepkg (as i wanted to keep the pkg around for distribution), and it built the package ok, but when i installed it, i found it was installed to /usr/local/bin, instead of the usual Arch style of /usr/bin.
I think you should review the part where it runs the configure script to include the flag --prefix=/usr
Actually, I'm not sure about this as, for instance, kde packages will by default detect the kde prefix and install there. Installing some KDE packages to non KDE prefixes breaks the packages. So on Arch /usr is not /opt/kde.
Perhaps I can read the makefile and determine if the package will be installed to /usr/local and modify the generated build files. This would only work for auto* but that would do. A lot of work though, so wouldn't be in the next version as I'm still working on broader issues.

Sorry for the delay, the rule for all the /opt packages (according to what i remember from Arch rules) is that big or propietary go there, but everything else goes to /usr.

I think you can narrow that applications list a lot because almost all KDE (official at least) and Gnome apps, are built by developers and go there, and wont usually need to be built by users. I think your program is most usefull for those other programs that there is no package... thats why i suggested the prefix, thats the one used for every non-gnome, non-kde, non-propietary other app... but if you can make it detect the type of app, thas much better!

But i could be wrong

mxcl · 2006-07-10 10:23:01

I will make the PKGBUILD have an additional step where it tries to identify the prefix and perhaps rewrites the Makefile (perhaps, as this method is not particulary simple and thus not safe). Probably for version 0.5.

Until then I suggest using wocka the alternate way, ie to checkinstall, as you get more control over the process that way.

snader · 2006-09-13 14:06:33

Wocka doesn't seem to work with .svn/entries files that are not in xml format, is that correct? Any workarounds for that?

mxcl · 2006-11-01 00:16:08

I'm not familiar with it being in any other format.

Can you provide an example of the other format, or even better, a cli command to get the revision number instead? Thanks!

Wocka 0.3 should come out sometime, really all that stopped it was demand, no users = no work..

meanimal · 2007-02-02 17:52:17

hey, I really appreciate this utility. I use it whenever possible for packages which don't already exist in Arch's repositories. It doesn't always work, and sometimes I have to play around with the name of the directory in which the source code is contained. I will start paying more attention to these scenarios so that it can be improved.

Thanks!

mxcl · 2007-02-12 14:50:14

I'm releasing a new version soon. So if there are any pressing issues, please write them here. Thanks

New version has bug fixes, some usage improvements and Qt dependency is removed.

waltm · 2007-02-12 18:32:36

It's worked for me. Would like someway of supplying a custom revision number. Thanks for the work.

mxcl · 2007-02-13 20:37:38

waltm wrote:

Would like someway of supplying a custom revision number.

The new version has --set-version and --set-name switches, for when Wocka gets it wrong, or you want to specify this stuff.

You can't specify the revision number though. But Wocka increments the revision on upgrades now.

If you tell me the use case for specifying the revision yourself. I'll add a switch for it, if it seems sensible.

meanimal · 2007-02-13 21:22:22

yay! --set-name will be useful.

waltm · 2007-02-15 02:08:19

mxcl wrote:

waltm wrote:
Would like someway of supplying a custom revision number.
The new version has --set-version and --set-name switches, for when Wocka gets it wrong, or you want to specify this stuff.
You can't specify the revision number though. But Wocka increments the revision on upgrades now.
If you tell me the use case for specifying the revision yourself. I'll add a switch for it, if it seems sensible.

The switches you are adding are what I want. I like to stick my initials in things I build so a pacman -Qs wjm will remind me of what I did. Dont need a custom revision switch then. When I used debian, the revision number was where such things could be done.

Keep up the good work ...

mxcl · 2007-02-17 02:14:25

Wocka 0.5 is released

I suggest some caution, as it's a rewrite. But I tested it quite thouroughly, and at least, all the bugs I knew about are fixed.

Also I removed the srcdir != builddir functionality. I'll reinstate this some time, and sooner rather than later if anyone actually used it. I removed it as it made the code hard to follow, and that just led to bugs.

Changes I can remember:

* Admitted defeat, added --set-name and --set-version switches
* Default install prefix for --pkgbuild is /usr
* Replaced --makepkg with --pkgbuild, and behaviour to only generate a
pkgbuild
* Fixed some minor bugs, improved robustness

Download
http://www.methylblue.com/wocka/packages/

mxcl · 2007-02-17 12:20:18

waltm wrote:

The switches you are adding are what I want. I like to stick my initials in things I build so a pacman -Qs wjm will remind me of what I did. Dont need a custom revision switch then. When I used debian, the revision number was where such things could be done.

This is a nice idea that I may adopt myself. I may add a config file for Wocka where you can specify such things.

meanimal · 2007-02-17 14:17:05

thanks for the new release!

mOLOk · 2007-02-18 17:29:14

If a package isn't in Arch repos nor in AUR, well, you should upload it in AUR and share it with the community or another person will look in the AUR, won't find it and will do the job you already did, twice.
I suggest to add the arch= tag into the automagically generated PKGBUILD (pacman3 requires it) and the license=
You may want to replace something like:
echo -e "\033[0;34m==>\033[0;0;1m Make \033[0;0m"
with:
msg "Make"

(msg is a function of makepkg)

mxcl · 2007-02-18 19:30:27

Thanks for the tip on msg(), didn't know that one. And I'll make the --pkgbuild option add licence and arch tags too, I'll get on with the next release.

With regard to not using Wocka because you should use AUR, as I say on the website; if you want to make a regular SVN checkout. Or an older package. Or maybe a new release for some app that is out just this second, and you don't much like makepkg* Then Arch and AUR may not help.

Wocka has other uses not catered by current Arch technologies as well.

I'm not insulting Arch. Arch is great! I just wanted a little more, so I scratched my itch.

But even if AUR and Arch provide, sometimes it's nice to do it all yourself! I'm a software developer and like to customise configure arguments. I also like to have complete control.

* I don't much like using makepkg as I want to do each of the build steps separately in case something goes wrong. I also don't want to maintain packages at the AUR really as I contribute to the community in other ways.

Last edited by mxcl (2007-02-18 19:35:10)

meanimal · 2007-02-18 19:43:36

I prefer to install everything on my system as Arch packages primarily because it keeps my system clean! I can easily remove the packages later without leaving any files behind.

Beyond that, I only contribute PKGBUILDs to AUR if I find the software useful and something I'm willing to maintain. Out of all the software I install that's not already in an Arch repo, this probably accounts for only 20%. The rest, I throw out pretty quickly, so wocka helps me experiment. For example, say you're having problems with the stable release of something already in an Arch repo, and you want to try the development branch? Try some experimental patches? There are dozens of cases where you wouldn't necessarily want to contribute (and maintain) a PKGBUILD.

mxcl · 2007-02-19 00:20:12

I'll prolly work on Wocka some more this week, so feature requests etc. are welcome and will influence direction.

ibendiben · 2008-01-25 19:35:15

How is wocka?
I can't find installwatch (dependecy)... but this seems an interesting project, I'd like to see some updates.

What about the other/similar projects:
bpkg
creapkg
pacinstall
versionpkg

Last edited by ibendiben (2008-01-25 19:36:36)

Piero Ferraz · 2008-06-13 00:52:05

HI, You can add the option not to confirmation?

example

wocka - noconfirm

------------
I have a simple script to update the amsn svn every day
I added the wocka on script
the problem is that every time for him to confirm the installation

want it automatic

----

My English is google translate

farvardin · 2008-09-16 12:25:08

it was a good utility, but now I can't compile it anymore

dmd -debug -ofwocka -odbuild/debug src/*.d
object.d: module object cannot read file 'object.d'

It may be related to the dmd compiler:
http://www.dsource.org/forums/viewtopic … b2a0f9cb68

will wocka be further developped ?

Daenyth · 2008-10-07 08:06:44

Well the last forum post was in Feb 2007, and the Wocka webpage was last updated April 2007, so I'd guess that it's not.

Arch Linux Tux · 2018-09-01 17:50:02

I think the page is down now. The program doesn't seem to be available anymore.

Last edited by Arch Linux Tux (2018-09-01 17:50:26)

ewaller · 2018-09-01 18:09:46

Arch Linux Tux wrote:

I think the page is down now. The program doesn't seem to be available anymore.

Well, it has been at least 10 years.

Please watch the dates on that to which you respond.
Thanks.

Closing

Arch Linux

#26 2006-07-04 10:40:07

Re: Wocka 0.5 - checkinstall for Arch Linux

#27 2006-07-07 23:11:25

Re: Wocka 0.5 - checkinstall for Arch Linux

#28 2006-07-07 23:45:20

Re: Wocka 0.5 - checkinstall for Arch Linux

#29 2006-07-10 10:23:01

Re: Wocka 0.5 - checkinstall for Arch Linux

#30 2006-09-13 14:06:33

Re: Wocka 0.5 - checkinstall for Arch Linux

#31 2006-11-01 00:16:08

Re: Wocka 0.5 - checkinstall for Arch Linux

#32 2007-02-02 17:52:17

Re: Wocka 0.5 - checkinstall for Arch Linux

#33 2007-02-12 14:50:14

Re: Wocka 0.5 - checkinstall for Arch Linux

#34 2007-02-12 18:32:36

Re: Wocka 0.5 - checkinstall for Arch Linux

#35 2007-02-13 20:37:38

Re: Wocka 0.5 - checkinstall for Arch Linux

#36 2007-02-13 21:22:22

Re: Wocka 0.5 - checkinstall for Arch Linux

#37 2007-02-15 02:08:19

Re: Wocka 0.5 - checkinstall for Arch Linux

#38 2007-02-17 02:14:25

Re: Wocka 0.5 - checkinstall for Arch Linux

#39 2007-02-17 12:20:18

Re: Wocka 0.5 - checkinstall for Arch Linux

#40 2007-02-17 14:17:05

Re: Wocka 0.5 - checkinstall for Arch Linux

#41 2007-02-18 17:29:14

Re: Wocka 0.5 - checkinstall for Arch Linux

#42 2007-02-18 19:30:27

Re: Wocka 0.5 - checkinstall for Arch Linux

#43 2007-02-18 19:43:36

Re: Wocka 0.5 - checkinstall for Arch Linux

#44 2007-02-19 00:20:12

Re: Wocka 0.5 - checkinstall for Arch Linux

#45 2008-01-25 19:35:15

Re: Wocka 0.5 - checkinstall for Arch Linux

#46 2008-06-13 00:52:05

Re: Wocka 0.5 - checkinstall for Arch Linux

#47 2008-09-16 12:25:08

Re: Wocka 0.5 - checkinstall for Arch Linux

#48 2008-10-07 08:06:44

Re: Wocka 0.5 - checkinstall for Arch Linux

#49 2018-09-01 17:50:02

Re: Wocka 0.5 - checkinstall for Arch Linux

#50 2018-09-01 18:09:46

Re: Wocka 0.5 - checkinstall for Arch Linux

Board footer