[ABANDONED][Project] Wakka: A Gtk-Based Package Management Tool

==Summary==
Wakka is a loosely-GtkPacman based package manager, designed to cleanup the design of GtkPacman as well as the user interface, and update it to the latest and greatest releases of Python and pyGtk. It was originally developed as a project to make GtkPacman more stable on my own system, but I realized that many other users had the same problems that I did, thus the public release.
==History==
I found GtkPacman when I first came to Arch in 2009, being the GUI loving Ubuntu convert that I was, and I noticed that the last release had been in February of 2008, with no updates since, and no indication that the project was ongoing. Being a budding (and overconfident) Computer Science student I decided to take on the task of forking and maintaining this wonderful piece of software for the community. Yes, I could finally give back! Little did I realize that the task was far beyond my skills to accomplish.
I quickly found that cleaning this thing up enough for my own use was hard enough, and getting a decent realease out and dealing with bug reports and such would be neigh on impossible. It also didn't help that I had no idea what the heck pacman was doing in the backend, since apt and Synaptic were my only prior experience with package managers.
So there I lost steam, but from time to time I would open the code up and peck away at it, modifying bits here and there to work the way I wanted, but I eventually just took to the command line and lost sight of old Wakka. Well, just this last week I stumbled back upon it, and with my newfound pacman-fu and python-jitsu (not to mention free time) I decided to tackle this beast once and for all. I may not keep it up to date when I'm finished, and I may not even use the thing, but I'm going to clean this monster up and make it faster, more stable, and most of all more elegant (have you looked at the code for gtkPacman? It's not very elegant).
==Installation and Use==
You can now install Wakka from the AUR, but if you still wish to download and try other versions, you can grab a source tarball of any release from the project page on google code or get the newest stable release from the link below. You can also grab the bleeding edge (sometimes broken) svn code as well, but it's not useful for much other than development purposes.
Basically, unless you're going to dig through the code, use the AUR version, it's the safest.
==Files==
Pkgbuild: http://aur.archlinux.org/packages.php?ID=47037
Project: http://code.google.com/p/wakka-package-manager/
Source: http://wakka-package-manager.googlecode … .4.tar.bz2
==TODO==
- Speeeeed it up!
- Streamlining
- Bugfixes
Not particularly in that order, depending on the circumstances.
Last edited by minasmorath (2012-04-12 18:22:08)

swanson wrote:Just did a daily update/upgrade and it worked very nicely indeed! All events present themselves clearly during the process. For me, as new Arch user, it is very nice to get a list of all available packages in the repos. The overview and search capabilties are handy, much more so than doing pacman -Ss "xxxxx" in terminal.
I'm glad you like it!
pablokal wrote:when you install something the sizes are not given of the packages to be installed (also the sizes of the dependencies); would be nice if these sizes were given, just like in pacman.
I didn't even notice that, I'll add it asap.
pablokal wrote:Second when installing by default the terminal is closed.
I don't know about opening it up, but you're right, hiding things is bad practice, so at least a summary and a more clear indication that stuff is going on.
tomd123 wrote:can you provide a PKGBUILD in the aur?
Hopefully I can get the PKGBUILD up in the AUR within the next week, but I won't post it until everything is ported to Python 3 and I've done thorough testing. I also have a couple minor changes to make along the way, I don't like the way the update all button works right now, I'm changing it so that it just marks all changes in the install queue and alerts you of the packages to be updated, and I need to fix the 'required by' section of the package summary, since it uses an old method, and dependency size display.
All in all as soon as it's cleaned up I'll post it. I'll be going on spring break here in a week as well so I'll have plenty of time to work on it this week and next.
Thanks for the input, I'm on it!
Mitch

Similar Messages

Pcurses - a curses package management tool

pcurses features package browsing and management in a curses frontend written in C++
Features:
* regexp filtering and searching any package property
* customizable colorcoding
* customizable sorting
* external command execution with package list string replacements
* user defined macros and hotkeys
Package management is done through external command execution: for example, '!sudo pacman -S %p' will install all currently queued packages.
For more information, read the README file at github and take a look at some of the defined macros in /etc/pcurses.conf.
Default hotkey mappings:
1 - filter packages with updates available
2 - filter installed packages
5 - run pacman -Syu
6 - run pacman -S on the current contents of the queue
7 - run pacman -Rs on the current contents of the queue
These macros are entirely customizable and are defined in /etc/pcurses.conf.
The default view optimized for 80x24 terminals:
And a 3 pane view for larger terminals:
Get it here: http://aur.archlinux.org/packages.php?ID=42685
Or, if you are using pacman-git: http://aur.archlinux.org/packages.php?ID=50804
Github: https://github.com/schuay/pcurses
Old thread from Nov 2010: https://bbs.archlinux.org/viewtopic.php?id=108585
For now, documentation is located mostly in the README file.
Keyboard commands are displayed by pressing the 'h' key in pcurses.
Last edited by schuay (2011-07-18 13:54:05)

Reposting the full tutorial from the README file:
QUICK TUTORIAL
Navigation and queue management
The package list and queue can be navigated using the up/down arrows, page
up/down, and the home and end keys. The tab key switches focus between the
package and queue lists.
Adding packages to the queue is done by pressing the right arrow key while the
package list is focused. Left arrow removes the selected package from the
queue.
Filtering
Keybindings are displayed by pressing the 'h' (Help) key in pcurses.
Filtering takes the following syntax:
nd:game 1 23
1 is a list of field specifiers. These tell pcurses which fields to search.
Field specifiers are the highlighted characters in the field names in the info
pane. In this example, this means that the Name and Description are searched
for the phrase 'game'.
2 the character ':' separates the field specifier list from the search phrase.
If this character is not present, the entire string is interpreted as the
search phrase.
3 is the actual search phrase. If it contains only alphanumeric characters, a
simple and quick string search is used. Otherwise, it is treated as a regular
expression (which is a bit slower). The search is case INSENSITIVE.
1 and 2 are OPTIONAL.
These searches can be chained. This means that a search for 'n:^a', followed by
'b:2010' will show all packages beginning with the letter 'a' and having a
build date in the year 2010.
Previous filters are cleared by pressing the 'c' key.
Pressing the up and down keys while in input mode will scroll through all
previous history.
Sorting and colorcoding
Colorcoding and sorting use the same syntax as filtering, but only accept a
single field specifier.
Command execution
Command execution can be entered by pressing the '!' key. The token '%p' will
be replaced by the current contents of the package queue. For example, with a
current package selection of pcurses and pacman,
!sudo pacman -S '%p'
will be expanded to
echo 'sudo pacman -S pcurses pacman'
A few useful commands could be
!pacman -Sy
!sudo pacman -S %p
!sudo pacman -Rs %p
Macros
Macros are defined in /etc/pcurses.conf using the syntax 'macroname=command'.
Macros can be chained by separating them with a comma. A few examples:
sortbyname=.n
colorbyrepo=;r
filterupdates=/d:update available
chainedmacro=@sortbyname,colorbyrepo,filterupdates
If defined, the macro named 'startup' will be executed on each application
start. Hotkeys can be defined by creating macros named '1', '2', [...], and are
triggered by pressing the corresponding key in pcurses.
All macros can be executed in pcurses by pressing the '@' key and entering the
macro name.
Last edited by schuay (2011-07-18 13:50:37)

Web-based user management tools???

Are there any pre-packaged or off-the-shelf tools one can use to manage unix users and groups in DS 5.2? (preferrably web based) I have found a few open source apps that are web-based but they don't seem to be production quality.
For now, I'm creating LDIF files and importing them or using the GUI console. This is tedius and the other sys admins that aren't familiar with ldap will find it difficult.
One of the open source tools I found was "Directory Administrator" which runs only under gnome, we don't use gnome.
Another tool is "LDAP Account Manager" which was originally built to manage samba users and their unix user/group attributes. We don't use samba and this application does not allow you to seperate the samba and unix components.
There has to be a simple web-based tool for managing unix users/groups. If any of you know of a commercial or free app, please let me know.

I urege to to take a look at phpldapadmin, an open-source php/web based tool for managing ldap/directory servers. We have been using it for over a year now, and find that it is easy to install, works well, and continues to receive updates on a periodic basis. Another nice thing is that since you have the php source, it's easy to modify for local modifications.
You can find it at:
http://phpldapadmin.sourceforge.net/

Package management

As far as I can see, 5.10 does not provide any new package management tools besides pkgadd/pkgrm.
This is an area where Solaris could really be improved.
blastwave.org/pkg-get is ok, but I what if I want to update bundled packages like SUNWapch*?
I may, for example, want to use the bundled packages for apache instead of csw, which installs everything under /opt, and is not compatible with the zones model which needs configuration state in /etc and data in /var
The only way to get hold of freshly updated SUNW packages (unless I am missing something) is to download .iso images via Software Express and extract them manually.
How about something similar to apt-get for native SUNW packages? Or at least the ability to wget the latest packages.
Please tell me I am an ignorant ape and there exists just such a solution.... ;-)

True ... the package management system "amazes" me.
I'm looking to install a few standard packages on a remote server but don't have a cd in drive ... where else online can i find those packages (like SUNWppror, SUNWpprou, and SUNWppro-plugin-sunos-base needed for smpatch)
Thank you.

FBWF Management Tool

I am installing Windows 7 Embedded POSREADY 7 and I cannot install the FBWF management tool.
I already installed winemb-registryfilter.cab, winemb-file-based-write-filter.cab, winemb-fbwf-wmi-provider.cab all through DISM but when I try to run the tool, it states the file-based writefilter management tool requires that version 6.1.7601.17649 or
greater of the File-based writefilter provider.
I am stuck! Am I missing something?

First did you re-install the language package after install these packages with DISM?
Second, Did you run Windows Update? - I thought the tool came down through Windows Update.
www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Package Management for CodeExchange ABAP projects

Hi CodeExchange ABAP Contributors,
according to the size of ABAP in the [https://cw.sdn.sap.com/cw/codex/projects|CodeExchange Project Directory Tag cloud] most of the Projects are ABAP based. Some of them like Twibap, ABAP JSON and ABAP OAuth depend on each other. That is also the case if you want to install packages using [SAPLink|http://code.google.com/p/saplink/], then you need in the most of the cases some [Plugin|http://code.google.com/p/saplink/wiki/pluginList] installed. That can be sometimes very cumbersome.
As a user of Perl, PHP and Ruby I was using their package management systems like CPAN, Pear and Gems. They provide an easy command line interface to install and update packages. In addition they take care about dependencies.
I think it's time to start working on a Package Management for CodeExchange ABAP projects. Let's call it ABAP Package Management (APM). SAPLink providing the container to exchange the package and ZAKE to handle the download and install can be a good starting point.
Let's discuss the problem space here and perhaps we also can involve someone who has perhaps already some experience in building a package management system.
Best regards
Gregor

Hi,
an XML file to be included into the nugg that describes dependencies on a base of Plugin ID, Plugin Name and Version should be enough.
The XML should be managed by SAPLink, the hard job is to automatically download and install the plugins.
How to login to CodExch?
How to download the certified version of the plugin? A project can delete an old version nugg.
As you said we need a central instance were the plugin version are versioned and identified univocally.
Indeed we need a page in code exchange or a tool in release page in order to register the current file as versioned.
Regards,
Ivan

Package management Smart ?

Did someone consider porting "Smart" package manager to Archlinux ? It currently supports rpm, Slackware tgz , and deb packages. On their web page they say "porting it to new systems should be very easy. " and in their words it resolve depedencies better than distros' native package managers.
Don't take it wrong, pacman is good. This is just a graphical interface of the already mature project based on GTK2. There is another graphical interface "Shaman" for Archlinux based on Qt libs, and to me it seems it has been abandoned. This "Smart" is under active development.
http://labix.org/smart
Last edited by picilli (2010-10-16 00:37:00)

picilli wrote:
Did someone consider porting "Smart" package manager to Archlinux ? It currently supports rpm, Slackware tgz , and deb packages. On their web page they say "porting it to new systems should be very easy. " and in their words it resolve depedencies better than distros' native package managers.
Don't take it wrong, pacman is good. This is just a graphical interface of the already mature project based on GTK2. There is another graphical interface "Shaman" for Archlinux based on Qt libs, and to me it seems it has been abandoned. This "Smart" is under active development.
http://labix.org/smart
Try packagekit if you want a gtk2/qt frontend, it works "OK".

Available APIs for process and package management

Hello All and welcome to my Hello All:
Welcome to my inaugural post. I am a complete noob to Solaris (although I have been using Linux for 5+ years) and am in the process of trying to get a handle on what local C/C++ APIs (if any) are available for management. Specifically, I am looking to find out about process and package management.
For process management, basically I would like to know is there some kind of interface to the the prstat application (ie. Memory and CPU utilization). Does something like this exist?
For package management, I am looking for the ability to add, remove, and query the package �database�. Correct me if I am wrong, but the Solaris package �database� seems similar to that of a Debian system (at least from the perspective that the informational files are stored as plain text in a well-defined directory [ie /var/sadm/pkg/]).
I have installed Solaris 10 on an x86 machine with a full installation; however, of the installed development kits (listed below) nothing jumped out at me.
-bash-3.00# ls -1d /var/sadm/pkg/*devel
/var/sadm/pkg/SUNWaspell-devel
/var/sadm/pkg/SUNWevolution-devel
/var/sadm/pkg/SUNWevolution-libs-devel
/var/sadm/pkg/SUNWgnome-a11y-base-devel
/var/sadm/pkg/SUNWgnome-a11y-libs-devel
/var/sadm/pkg/SUNWgnome-a11y-reader-devel
/var/sadm/pkg/SUNWgnome-a11y-speech-devel
/var/sadm/pkg/SUNWgnome-audio-devel
/var/sadm/pkg/SUNWgnome-base-libs-devel
/var/sadm/pkg/SUNWgnome-camera-devel
/var/sadm/pkg/SUNWgnome-common-devel
/var/sadm/pkg/SUNWgnome-component-devel
/var/sadm/pkg/SUNWgnome-config-devel
/var/sadm/pkg/SUNWgnome-desktop-prefs-devel
/var/sadm/pkg/SUNWgnome-file-mgr-devel
/var/sadm/pkg/SUNWgnome-hex-editor-devel
/var/sadm/pkg/SUNWgnome-img-editor-devel
/var/sadm/pkg/SUNWgnome-libs-devel
/var/sadm/pkg/SUNWgnome-media-devel
/var/sadm/pkg/SUNWgnome-panel-devel
/var/sadm/pkg/SUNWgnome-pilot-devel
/var/sadm/pkg/SUNWgnome-print-devel
/var/sadm/pkg/SUNWgnome-project-devel
/var/sadm/pkg/SUNWgnome-terminal-devel
/var/sadm/pkg/SUNWgnome-text-editor-devel
/var/sadm/pkg/SUNWgnome-vfs-devel
/var/sadm/pkg/SUNWgnome-wm-devel
/var/sadm/pkg/SUNWgnutls-devel
/var/sadm/pkg/SUNWjpg-devel
/var/sadm/pkg/SUNWlibexif-devel
/var/sadm/pkg/SUNWlibgcrypt-devel
/var/sadm/pkg/SUNWlibpopt-devel
/var/sadm/pkg/SUNWmozilla-devel
/var/sadm/pkg/SUNWmoznspr-devel
/var/sadm/pkg/SUNWmoznss-devel
/var/sadm/pkg/SUNWogg-vorbis-devel
/var/sadm/pkg/SUNWopenjade-devel
/var/sadm/pkg/SUNWopensp-devel
/var/sadm/pkg/SUNWpcsclite-devel
/var/sadm/pkg/SUNWpng-devel
/var/sadm/pkg/SUNWpostgr-devel
/var/sadm/pkg/SUNWPython-devel
/var/sadm/pkg/SUNWTiff-devel
I've placed orders for Solaris Internals and Solaris Performance & Tuning (that should arrive tomorrow), but I was hoping that someone could give me a gentle push (or perhaps a swift kick) in a general direction. :)
Thanks.

For process management, basically I would like to
know is there some kind of interface to the the
prstat application (ie. Memory and CPU utilization).
Does something like this exist?Not prstat (although you could 'truss' it and see some of what it's doing to collect the information). kstat is available with a C interface and through perl/shell. It has several CPU fields. It's certainly useful for monitoring, but read-only. I'm not sure what you're looking for in terms of "management".
Also 'dtrace' can provide tons of dynamic information, but that's not necessarily what you're looking for.
For package management, I am looking for the ability
to add, remove, and query the package �database�.
Correct me if I am wrong, but the Solaris package
�database� seems similar to that of a Debian system
(at least from the perspective that the
informational files are stored as plain text in a
well-defined directory [ie /var/sadm/pkg/]).Yes, although it's based on the SysV packaging system. I don't believe there's any API for it outside of the 'pkg*' utilities.
Darren

"manage nuget packages for solution" is missing in the drop down for NuGet Package Manager

Hi,
I have VS2013 Ultimate on windows 7 PC and that Nuget Option does show in the dropdown. Today, I setup a vm in Azure, from image I select VS2013 Ultimate, just like the one on my PC. However, when I click on the Tools, Nuget, there is only 2
drop down option, "package manager console" and "package manager settings" are the only 2 available. How can I get the ""manage nuget packages for solution"?
I want to install the xamarin.forms extension and I need this.
thank you
Thank you

Hi laJasmine,
Based on your issue, generally, I know that there have two ways to see the "manage nuget packages for solution" option after we install the VS2013 Ultimate.
One way is that it is default that we can see the "manage nuget packages for solution" option by right click this Solution->Manage NuGet Packages for Solution option like the following screen shot.
Another way is that we can see the "manage nuget packages for solution" option by clicking the Tools->Library Package Manager-> manage nuget packages for solution like the following screen shot.
So please check if you can get the "manage nuget packages for solution" option from this above two way again.
If you still could not the "manage nuget packages for solution" option in this VS2013 Ultimate, to check if this issue is related to the VS2013 Ultimate set up file. I suggest you could try to copy this setup file and then install it on other machine
and then check if you still get the issue.
If you have any updated message about this issue, please tell me.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Unified Package Manager/Format

I know that this topic is not a new one, but I thought it might be interesting to bring it up once again.
The reason that I'm suddenly interested in a unified package manager/format, is that I just saw Bryan Lunduke rant about it, and I thought to my self: "Hey, that makes sense!"
Bryan Lunduke is not someone I usually hold in high regard, but I was intrigued and started googling. To my surprise I found that there wasn't much interest in the subject.
Now, to you that may make perfect sence, but to me it's absolutely mindboggling. After all, the only reason I'm still sticking with Arch Linux, is the ABS. Not that I don't care for Arch, I really do, but I spend far to much time configuring it, rather than using it.
So what are the arguments for and against?
The arguments against is easy if you ask me:
PRIDE
Yes I said it: "We're happy with out system and it works damn you!"
So, it works... Well, so does a bike, but quite often you'd probably like to take your car instead. Maybe it's raining, maybe the distance is great. Who cares, the point is that the fact that it works, doesn't mean that it could not potentially work quite a lot better.
Back on topic.
Arguments for, is a bit harder, not least because I'm not as much of an expert on the subject as I'd like to be, but I think they're plentiful.
I would assume that developers would appreciate this.
If a set of tools, like the ABS, was included by default, that would indeed make me happy.
Maintenance of packages for multiple platforms would become quite a lot easier, if not trouble free.
And so on and so forth.
I suspect you will be more than able to help filling out the list.
In the end though, my biggest problem is that people ask for a reason to begin work on such a thing. My counter argument of course it: "Why the hell not?!" Arch Linux already provide the perfect foundation, i.e. pacman and ABS. Of course for cross platform compatibility, some work has to be done, but the greatest problem, I believe, is convincing the community that this is a worth while effort.
Oh well, enough ranting I suppose. I really just wanted to revive this debate, as I personally find it rather important. I don't have all the answers, but I dare you to come up with a problem that I cannot provide a theoretical solution to. To me it all seem so simple, and it's a mystery that this feat has not been achieved many years ago.
Best regards.
NB:
I'm not so arrogant that I do not appreciate that I may be entirely on the wrong track, but please, if that is indeed the case, do try to enlighten me rather than something uncomfortable.

Trilby wrote:
You beat me to that XKCD comic. It's good for a chuckle, but hopefully that doesn't make anyone think that's all it's good for. That comic captures the primary (and perhaps only) reason I'd never have any hope in such a cause.
Just look at attempts an universal language. You'd be hard pressed to find a handful of people in your day to day interactions who ever really learned esperanto, for example (I think I know one, but I haven't seen him in years). Now we can set standards, though. The arch linux forums have selected English as our default language - and in a sense we force speakers of other languages to use English ... in a sense, but not in another sense. There are various arch linux online communities in other languages, where some other language is the default. So one community can set a standard and try to enforce it, but that can't stop another community from springing up and using something different.
So if we say Arch linux's package format is the one package format to rule them all, fine. But then we have to convince others. Even if we convinced a lot of debian and red hat people, for example, we'd probably have to compromise a bit and we'd end up with an arch-pm-deb package. I'm sure some debian and redhat developers would fork their project or start new distros that continued to use .deb/.rpm, and some archers would conclude that this compromise was just a failure and they'd go on using pkg.tar.gz. And then we have the exact situation of the XKCD comic.
Sure, the world would be much simpler if one person could make an arbitrary decision based on their own preference and have everyone else in the world follow it. But that's not our world - and I'm glad it's not.
I'm usually not much for compromises (more on that on another occasion), but in this case I'm all for it, as long as it's sensible compromises. I have no illusions that the Arch way is the perfect way, and in any case, certain changes would need to be make to make it work.
I would suggest that some may misunderstand my intentions. I see no reason my the average Debian, OpenSuse, Mint, *buntu, Fedora, Gentoo (etc.) user should experience any change. A Debian user would still use apt-get install package, or whatever graphical front end he or she desires, as with most other distributions, possibly excluding Gentoo and such.
My interests are limited to the back end system end the tools that are provided by default, like something similar to ABS.
Last edited by zacariaz (2013-08-17 15:09:31)

Tag-based package system

Hello,
I'd like to share one interesting idea (as I think ) with you. I've googled a little and looks like there is no distr, where this feature was implemented. Correct me, please, if I'm wrong and if this idea was offered earlier. And sorry for my no so good English
I think that tags were really perfect idea and everybody can see how tags work in web, music, video etc. Tag-based file systems is another one step to absolutely convenient life of ordinary user and there some works around it (https://blueprints.launchpad.net/ubuntu … filesystem).
I offer you similar (in some way) thing: add tags support to pacman. Look: if I'm a c++ programmer I'm definitely interested in everything connected with c++, i.e. compiler, build system, IDE, source checking utils, indexing system etc. Let's tag then g++, netbeans, scope, kscope with tag c++. I'm sure that everyone reading this post imagined a few more tags for packages that I enumerated: compiler for g++; ide, c, ruby, uml and java for netbeans; c, java, python, perl, php for cscope.
Tags will make searching simple as never: if I need for example GTK image viewer that supports EPS and looks like photoshop, i just run 'pacman -Q --tags "gtk, image viewer, eps, photoshop"' and I will see gimpshop. Of course many of you already know that it is gimpshop, but for newbies (and not only them) tags will greatly help searching.
In PKGBUILD tags will just look like: tags="sex, drugs, r'n'r"
It would be great if somebody tell what he (she) think about it.
Thanks.
Best Regards,
Dmitry Vinokurov
Last edited by Raydan (2009-08-20 18:32:19)

this has been discussed to death already
we already have on old bug report, with many comments : http://bugs.archlinux.org/task/7132
a part of the last comment was :
Allan wrote:Dusty said: Every piece of meta-data on a PKGBUILD makes it that much more work to maintain.
True, what portion of packages actually have a changelog?
So even if pacman had this feature, it would take ages to define meaningful and consistent tags on all packages.
ngoonee's idea is not bad, as it would allow to have this effort community-driven rather than developer-driven.
Allan wrote:The question should be: is there a want/need for this in package management with pacman? Whether or not Arch makes use of such a feature is beside the point.
So I say someone should implement this if they really want to...
actually a patch was written, by Ronald van Haren aka pressh, but this patch introduced a lot of duplication between group and tags code, as these two are quite similar.
and anyway, if Arch is not going to make use of that feature, or use it poorly, because adding and maintaining tags is too much work, there is not a real need to bother implementing this feature properly.
but again ngoonee's proposal of implementing this outside of pacman solves that problem too.
So to sum up, if you want tags, just do it
Last edited by shining (2009-08-21 09:48:38)

Visual Studio 2013 Nuget Package Manager error

Hello everyone,
I tried to add and use OpenCV library in my Visual Studio javascript windows application project, but I still get the same error.
This is my Package manager console:
PM> Install-Package OpenCV
Installing 'OpenCV 2.4.8'.
Successfully installed 'OpenCV 2.4.8'.
Adding 'OpenCV 2.4.8' to BlankSharedApp1.Windows.
Uninstalling 'OpenCV 2.4.8'.
Successfully uninstalled 'OpenCV 2.4.8'.
Install failed. Rolling back...
Install-Package : Could not install package 'OpenCV 2.4.8'. You are trying to install this package into a project that targets 'Windows,Version=v8.1', but the
package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1
+ Install-Package OpenCV
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], InvalidOperationException
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
Thanks for answers.

Hi Fačko,
Normally, we won't get any errors if we create a new project. Since you get this error when using OpenCV library and it is a third-party product, I think you need to ask in
OpenCV forum for better response.
Thank you for your understanding!
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Project management tools for complex publishing project?

I was wondering what project management tools people use for managing complex InDesign projects? Software-oriented project management tools, or are there tools specifically for publishing projects?

The "Yes" is a link to a list of them. There are also a number of web-based services like 37 Signals.

Slackware user - Arch install process and package management questions

I currently am using Slackware 12 with updates. It has become increasingly cumbersome to compile new software given the number of dependencies that also have to be compiled, and have their own dependencies compiled, etc and so on.
Other than the fact that the adoption of new packages is somewhat glacial, and that there is no automatic dependency resolution, I really like Slackware. Its fast, relatively easy to configure, and easy to use. I'm conversant in commandline-ese.
I've been led to understand based on the Arch wiki that Arch is very similar to Slackware in its layout, but with bleeding edge packages and dependency resolution, so I would think it would be about perfect.
However, I also understand that the install is more difficult that Slackware. How much more so is my question. Is it impossibly confusing and unhelpful like Debian installation was, or just slightly more difficult than Slackware or FreeBSD (both of which have very smooth installation scripts)
Also, for packages that have to be compiled from source, are dependancies easy to satisfy from the arch repository, or do dependencies for new software have to be compiled with their dependencies.
I'd probably just be trashing everything but /home, and doing a clean reinstall.
Is Arch the right distro for me, or am I better off staying with Slackware? Like I said, I really like Slackware except for the package management issues.

I've been led to understand based on the Arch wiki that Arch is very similar to Slackware in its layout, but with bleeding edge packages and dependency resolution, so I would think it would be about perfect.
You are right about that.
However, I also understand that the install is more difficult that Slackware. How much more so is my question. Is it impossibly confusing and unhelpful like Debian installation was, or just slightly more difficult than Slackware or FreeBSD (both of which have very smooth installation scripts)
They are quite similar, but Slackware provides more help when doing tasks like - how can I partition my harddisk and so on. But If you're comfortable with Slack's install procedure then installing Arch is much easier, just read the install guide.
I think Arch is good for you, because currently I have both - Slackware and Arch and both suit me fine for my needs.
Also remove all *. entries in your /home

Is adjusting permissions for LightRoom based archive management worthwhile?

I'm trying to set up an archive that is managed through a LightRoom Catalog. I was wondering if anyone has done this before and adjusted the permissions of their files to read only to ensure that LightRoom Catalog metadata changes do not alter or get saved to files.
I plan to have the archive set up in 3 locations with copies of the LightRoom Catalog. I will need to be able to add keywords and collections to a catalog at 2 of the locations. I am interested in using permissions to ensure that the catalog is the only file that needs to travel between the locations. I don't want to get into a situation in which altering the LightRoom Catalog might alter files and necessitate that I either save new metadata to files with each keyword/collection addition or that I regularly synchronize the entire archive to ensure all 3 copies of the archive are mirrors of one another.
I have three serious concerns about the longterm viability of managing file permissions:
1. I worry that it will be difficult to manage the user/s who have the privileges to manage these permissions and that it will be difficult to do so in different locations and on different computers
2. I worry about whether permissions management might introduce some form of file corruption
3. I worry about the time involved in altering an entire archives worth of permissions to read only and the time involved in reversing this every time I want to unarchive content for new projects
I have also posted this question to Luminous Landscape here: Adjusting Permissions for LightRoom Catalog Based Archive Managment. Worthwhile?

... and adjusted the permissions of their files to read only to ensure that LightRoom Catalog metadata changes do not alter or get saved to files.
By default, Lightroom does not write anything to your photo files. Of course, there's no way to prevent a user from changing this default behavior and writing information to the files. I suppose making the directories read-only helps, but people could still change that. If the directories are on a server, then only the server admin could change the permissions.
2. I worry about whether permissions management might introduce some form of file corruption
I never heard of such a thing, but this is an operating system issue, not a Lightroom issue.
I worry about the time involved in altering an entire archives worth of permissions to read only and the time involved in reversing this every time I want to unarchive content for new projects
I don't think you understand how Lightroom works. There would be no need to reverse anything to "unarchive" the content — although in my opinion, the idea of "archiving" content in the first place doesn't feel right ... if the photos are imported into Lightroom at one time, leave them in Lightroom, don't go through an archive process removing the photos from Lightroom followed by unarchive process, that is something that is ineffective and causes numerous problems with non-expert users. When you import photos into Lightroom, the photos still remain on your hard disk somewhere, Lightroom does not actually keep a copy of the photo. Lightroom keeps pointers to the photo's locations and stores any metadata and edits. Removing a photo from Lightroom (archiving) is the equivalent of deleting the metadata and edits, and I cannot see a reason to do that.
So, bottom line, to answer your title question, "Is adjusting permissions for Lightroom based archive management worthwhile?" — without further discussion of your setup and goals, I see no reason to even spend your time on this, unless you are the server admin of the location where the photos are stored, in which case then the answer is go right ahead and make them read-only.

[ABANDONED][Project] Wakka: A Gtk-Based Package Management Tool

Similar Messages

Maybe you are looking for