From the discussion with Vaclav Tunka it would be good to introduce
assistant which prepares the JBOSS environment on Fedora.

Vaclav Tunka should provide more details what steps are needed for
proper functionality

We would discuss about this.

Currently, running da prep devassistant installs dependencies only for Python 2 development. Python 3 flag (or Include also Python3 dependencies flag) should be included as well.

The assistants/crt/c.yaml and assistants/crt/cpp.yaml files list eclipse-rpm-editor in dependencies_build

This means attempting to build an RPM using da will try to install the entire eclipse-cdt suite, openjdk, ant, hamcrest and dozens of other packages I don't want or need.

Is that really necessary just to build an RPM from a spec file for a project that is pure C or C++?

It'd be cool to have an assistant that would create a simple impress.js presentation.

I don't think autoconf and automake are needed to build the RPM. They are needed to regenerate the configure script, but not to run it, which is all the specfile needs to do.

Most GitHub errors (bad publickey etc.) are not caught because the handling in this assistant is not present, and only the cd $dirname command on line 48 fails. This shouldn't be the case, and all errors from git should immediately be caught.

In c.yaml, cpp.yaml, ruby/rails.yaml and php/lamp.yaml, there are cl_f commands that do not work and should be replaced with cl_i.

While the user is presented with the option to create the project in any directory they want (as usual with other assistants), the result is always put into ~/public_html/$basename.

Fixing this issue comprises of fixing both php/lamp.yaml, but also the apache_config.sh script it uses.

manpages/da.1 and manpages/devassistant.1 are almost identical, but as far as I can tell edits have to be made to both and kept in sync.

The devassistant.1 file should be auto-generated from the other one.

The files/crt/c/cdevelopmenttool.spec file and the C++ equivalent have this changelog:

* Fri Mar 15 2013 UserName
- first Version

When the project is created the date and name should be replaced with more meaningful values. On POSIX platforms the user's name can be obtained with pwd.getpwuid(posix.getuid()).pw_gecos

Simply executing an attached assistant could be a security risk. I think the user should be required to explicitly affirm their willingness to execute the .devassistant script attached to the upstream project before the actual execution, possibly with the option to review the sources. Alternatively, we could perform some sanity checks.

DevAssistant needs a YUM-equivalent DNF assistant to be able to run meaningfully under Python 3.

Here's what happens if I create a Django project, using python 3 and virtualenv, on Fedora 21 Alpha:

I suspect the problem is that F21 uses python 3.4, where virtualenv is bundled with python: https://docs.python.org/3/library/venv.html

This assistant has aim to include some libraries into C/C++ source codes without and user interaction.
Just enter library which you would like to add into project.

Vim is not needed to develop in C/C++. That's a fact. When I run da crt cpp foo it fetches vim. I consider it annoying as I wont use it.

• Why is there a dependency on vim-enhanced and vim-X11?
• Could you remove it?

Thanks

Hi. We could use a Reveal.js assistant as it is simple enough to make, and would be of a great benefit. Additionally, it could deploy to OpenShift's Reveal.js cartridge (requiring addition of OS helpers in the core, presumably).

In order to promote dap index, we have to provide a way to easily create an assistant.

I suggest a crt assistant that would accept switches like --crt --mod --prep --snippet, etc. and would create a repository like this one https://github.com/3DprintFIT/dap-openscad

And then mod assistant, that would do this:

https://github.com/3DprintFIT/dap-openscad/blob/master/dapgen.sh

(in a more sophisticated way)

RPM or for cpan? devassistant/devassistant#113

The template-gui.py file that is referenced in the log as executable in fact isn't so.

Assistant should help me, not introduce more stuff to annoy me. C++ assistant creates some classes I won't use and README content to delete.

While this would be a good "How to code in C++" assistant, it is absolutely useless for new C++ projects. Filtering garbage form useful content is more time consuming than creating the project from scratch without DA.

• Remove all example garbage
• Keep the assistant useful and ready to use

I think that all this also covers the C assistant.

I think that when da-gui is run from the .desktop file, the assistant in %subj% should not fall back to ~ as the default path. The reason is that the use case:

Open DevAssistant from menu > create GitHub repo for a project stored in your ~

simply makes no sense at all. I believe the assistant should not launch unless a path is specified, much like it is the case with creator assistants' names.

However, I am not sure how much programming effort would go into this, so I am marking this as enhancement rather than a bug.

%subj, namely the dash. When you create a project with a dash in its name, it gets created properly. However, since manage.py imports from the directory whose name is the same, it fails due to dash being in the imported name.

I suggest DA either fail when illegal character is entered in the project name, or convert these characters to legal ones where necessary.

Otherwise it leads to an error right away.

The assistant advises to run rails s, but that leads to an error about missing deps.

Since pip doesn't honour filesystem permissions when installing from tar (Issue pypa/pip#1146, fix not present e. g. in Fedora), the assistant in %subj% fails with Permission denied on the apache_config.sh source file.

On first run, it succeded, but the project directory is empty.
On second run, it fails with:

Creating GTK+ 3 project test3 in /tmp ...
cp -r /home/msuchy/projects/devassistant-assistants-fedora/files/crt/python/gtk3/. "test3"
On branch master
nothing to commit, working directory clean

Most of the fixes in issue #29 would have been found much sooner if the example makefiles enabled compiler warnings. It is very bad to give examples to beginners that don't turn on warnings.

The configure.ac files include this:

AM_INIT_AUTOMAKE([-Wall -Werror])

but it doesn't get into the final makefiles.

da-gui shows weird character when creating ruby project
See the output:

    Resolving RPM dependencies ...
Creating Ruby on Rails project ruby in /tmp ...
rails new "ruby" --skip-bundle
�[1m�[32m      create�[0m
�[1m�[32m      create�[0m  README.rdoc
�[1m�[32m      create�[0m  Rakefile
�[1m�[32m      create�[0m  config.ru
�[1m�[32m      create�[0m  .gitignore
�[1m�[32m      create�[0m  Gemfile
�[1m�[32m      create�[0m  app
�[1m�[32m      create�[0m  app/assets/javascripts/application.js
�[1m�[32m      create�[0m  app/assets/stylesheets/application.css
�[1m�[32m      create�[0m  app/controllers/application_controller.rb
�[1m�[32m      create�[0m  app/helpers/application_helper.rb
�[1m�[32m      create�[0m  app/views/layouts/application.html.erb
�[1m�[32m      create�[0m  app/assets/images/.keep
�[1m�[32m      create�[0m  app/mailers/.keep
�[1m�[32m      create�[0m  app/models/.keep
�[1m�[32m      create�[0m  app/controllers/concerns/.keep
�[1m�[32m      create�[0m  app/models/concerns/.keep
�[1m�[32m      create�[0m  bin
�[1m�[32m      create�[0m  bin/bundle
�[1m�[32m      create�[0m  bin/rails
�[1m�[32m      create�[0m  bin/rake
�[1m�[32m      create�[0m  config
�[1m�[32m      create�[0m  config/routes.rb
�[1m�[32m      create�[0m  config/application.rb
�[1m�[32m      create�[0m  config/environment.rb
�[1m�[32m      create�[0m  config/environments
�[1m�[32m      create�[0m  config/environments/development.rb
�[1m�[32m      create�[0m  config/environments/production.rb
�[1m�[32m      create�[0m  config/environments/test.rb
�[1m�[32m      create�[0m  config/initializers
�[1m�[32m      create�[0m  config/initializers/backtrace_silencers.rb
�[1m�[32m      create�[0m  config/initializers/filter_parameter_logging.rb
�[1m�[32m      create�[0m  config/initializers/inflections.rb
�[1m�[32m      create�[0m  config/initializers/mime_types.rb
�[1m�[32m      create�[0m  config/initializers/secret_token.rb
�[1m�[32m      create�[0m  config/initializers/session_store.rb
�[1m�[32m      create�[0m  config/initializers/wrap_parameters.rb
�[1m�[32m      create�[0m  config/locales
�[1m�[32m      create�[0m  config/locales/en.yml
�[1m�[32m      create�[0m  config/boot.rb
�[1m�[32m      create�[0m  config/database.yml
�[1m�[32m      create�[0m  db
�[1m�[32m      create�[0m  db/seeds.rb
�[1m�[32m      create�[0m  lib
�[1m�[32m      create�[0m  lib/tasks
�[1m�[32m      create�[0m  lib/tasks/.keep
�[1m�[32m      create�[0m  lib/assets
�[1m�[32m      create�[0m  lib/assets/.keep
�[1m�[32m      create�[0m  log
�[1m�[32m      create�[0m  log/.keep
�[1m�[32m      create�[0m  public
�[1m�[32m      create�[0m  public/404.html
�[1m�[32m      create�[0m  public/422.html
�[1m�[32m      create�[0m  public/500.html
�[1m�[32m      create�[0m  public/favicon.ico
�[1m�[32m      create�[0m  public/robots.txt
�[1m�[32m      create�[0m  test/fixtures
�[1m�[32m      create�[0m  test/fixtures/.keep
�[1m�[32m      create�[0m  test/controllers
�[1m�[32m      create�[0m  test/controllers/.keep
�[1m�[32m      create�[0m  test/mailers
�[1m�[32m      create�[0m  test/mailers/.keep
�[1m�[32m      create�[0m  test/models
�[1m�[32m      create�[0m  test/models/.keep
�[1m�[32m      create�[0m  test/helpers
�[1m�[32m      create�[0m  test/helpers/.keep
�[1m�[32m      create�[0m  test/integration
�[1m�[32m      create�[0m  test/integration/.keep
�[1m�[32m      create�[0m  test/test_helper.rb
�[1m�[32m      create�[0m  tmp/cache
�[1m�[32m      create�[0m  tmp/cache/assets
�[1m�[32m      create�[0m  vendor/assets/javascripts
�[1m�[32m      create�[0m  vendor/assets/javascripts/.keep
�[1m�[32m      create�[0m  vendor/assets/stylesheets
�[1m�[32m      create�[0m  vendor/assets/stylesheets/.keep
Ruby on Rails project ruby in /tmp has been created.
To run the application use: rails s
For more information about Ruby on Rails project visit <u>http://rubyonrails.org</u>

When using -b to build an RPM cpp.yaml unconditionally runs yum-buildep as root.

If all the BuildRequires packages are already installed this is unnecessary, but the user has to enter the root passwd or the build fails.

The user might not know the root password, and it isn't needed to run rpmbuild, so it should only be requested when there are missing packages. The BuildRequires can be queried with:

rpmspec -q --buildrequires foobar.spec

and each package can be checked for.

Shows $github_login, should show actual login name.

Reproducer:

1. Make sure python-django14 is installed and python-django is not installed.
2. run python/django assitent

It fails with:

/bin/sh: django-admin: command not found

That is because python-django14 provides python-django, but does not provide /usr/bin/django-admin and instead provides /usr/bin/django14-admin