[Dev] Acerca de libretools/About libretools

[Joshua Ismael Haase Hernandez]

A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20120919/d75eeed6/attachment.sig>
-------------- next part --------------
Intent? hacer un buen PKGBUILD para [chiliproject] [] ([el que encontr? en AUR] [chili aur] apesta).

Libretools _era_ perfecto para esa tarea `aur ruby-rails` pero al parecer `aur` intenta usar `vimdiff` y falla sin avisar. ?No deber?an instalarse las dependencias autom?ticamente? ?o manejar el caso de que no est?n instalados?

Creo que __es un problema que modifiquemos los scripts para uso personal cuando deber?an ser gen?ricos__.

Adem?s tenemos 3 de 8 puntos en [el test de Joel Spolsky] [Joel test] (4 preguntas no aplican):

1. Control de versiones.
2. Empaquetado en un paso.
3. Base de datos para errores.

Pero nos falta:

4. Arreglar errores antes de hacer c?digo nuevo.
5. Agenda al d?a.
6. Especificaciones.
7. Control de calidad.
8. Pruebas de usabilidad.

Yo agregar?a:

9. Documentaci?n efectiva y actualizada.

Creo que __es importante hacer algo al respecto porque los scripts se est?n volviendo dif?ciles de mantener__ (`toru` no funciona, un mont?n de c?digo duplicado...) __y adaptados al estilo de uso de__ unos __pocos__ (?`vimdiff` obligatorio en `aur`?).

No voy a hacerlo inmediatamente, pero empiezo con las especificaciones de `fullpkg` y sus pruebas unitarias. A prop?sito, https://bugs.parabolagnulinux.org/ est? ca?do.

---
I tried to do a good PKGBUILD for [chiliproject] [] ([the one on AUR] [chili aur] sucks).

Libretools _was_ perfect for that task `aur ruby-rails` but it seems like `aur` try to run `vimdiff` and fails without notice. Shouldn't dependencies be managed automatically? Or handle the missing program?

I think __modifying scripts for personal use when they should be generic is a problem__.

Also, we have 3 from 8 points in [Joel Spolsky's test] [Joel test] (4 questions do not apply):

1. Version Control.
2. One step packaging.
3. Bug database.

We are missing:

4. Fixing bugs before writing new code.
5. Up to date schedule.
6. Specs.
7. Quality Assurance.
8. Usability tests.

I would add:

9. Effective and updated Docs.

I think __it's important to do something about it because libretools is getting hard to maintain__ (`toru` is broken, a lot of duplicated code...) __and adapted to few's personal workflow__ (forced `vimdiff` on `aur`?).

I'm not going to start inmediately, but I'm starting with `fullpkg` specs and it's unit tests. BTW, https://bugs.parabolagnulinux.org/ is down.

[chiliproject]: https://www.chiliproject.org/
[chili aur]: https://aur.archlinux.org/packages.php?ID=60338
[joel test]: http://www.joelonsoftware.com/articles/fog0000000043.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20120919/d75eeed6/attachment.html>