Re: default config machinery

2012-04-19 Thread Marco Martin
On Monday 16 April 2012, Marco Martin wrote:
 Hi all,
 
 we now have a plasma-mobile-config git repo (where different devices would
 be different branches) that has also the startactive modules, since they
 may be device dependent as well.

to update this, now i have 

plasma-contour-config
plasma-contour-config-meego 
plasma-contour-config-vivaldi

building from the different branches


i would still try to rename
kde-skel-binary
to
nepomuk-default-database-skel (since is what it is)

and try to keep the startactive modules in startactive (hopefully not many 
device specific changes will be needed?) tomake a tad easier to package

then i would really like to merge this asap in devel (if continuous 
integration out of the different branches can be enabled would be awesome)

Cheers,
Marco Martin
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


Re: default config machinery

2012-04-19 Thread Lamarque V. Souza
Em Thursday 19 April 2012, Marco Martin escreveu:
 On Monday 16 April 2012, Marco Martin wrote:
  Hi all,
  
  we now have a plasma-mobile-config git repo (where different devices
  would be different branches) that has also the startactive modules,
  since they may be device dependent as well.
 
 to update this, now i have
 
 plasma-contour-config
 plasma-contour-config-meego
 plasma-contour-config-vivaldi
 
 building from the different branches
 
 
 i would still try to rename
 kde-skel-binary
 to
 nepomuk-default-database-skel (since is what it is)

 I think we should follow a standard to name packages. Above you used 
the customization strings (device name / operating system) as suffix (e.g. 
plasma-contour-config-meego), here you used the customization string (default) 
in the middle of the package name. nepomuk-database-default would be a better 
name (or just nepomuk-database if we really follow the standard for plasma-
contour-config). Then we can use nepomuk-database-vivaldi, nepomuk-database-
something else. The skel is not necessary in my oppinion. If you check you 
will see that other packages install files in /etc/skel without having skel 
in their names.
 
 and try to keep the startactive modules in startactive (hopefully not many
 device specific changes will be needed?) tomake a tad easier to package

+1. I prefer keeping configuration files near the programs that use 
them 
(if possible).

-- 
Lamarque V. Souza
http://www.basyskom.com/
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active