Re: default config machinery
Em Tuesday 24 April 2012, Marco Martin escreveu: > Hi all, Hi, > > another thing i would like to know a bit more opinions about using > /etc/skel for the default nepomuk db vs its own folder in /usr/share, in > the end is a matter of preference on how the home initialization will be > done. /etc/skel is ok for me, it exists for that kind of thing. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: default config machinery
Hi all, update on this issue: now the new default config is in devel, with the new skel based way , there is a default one (that would be mer) and a meego specific one, they are alternatives. for now the meego and mer ones are the same, will be differentiated when the meego kickstart changes. the vivaldi specific plasma-contour-config package is here: https://build.pub.meego.com/project/show?project=Project%3AKDE%3AMer_Extras%3AAdaptation%3AVivaldi anything vivaldi related could be just put in that project, as the archosg9 project etc (ideally delta should be kept as tiny as possible) right now everything should still just work, needs a bit of testing then the change can be finished by enabling continuous integration on the various branches so having an automagic way to have always up to date default configs for every device another thing i would like to know a bit more opinions about using /etc/skel for the default nepomuk db vs its own folder in /usr/share, in the end is a matter of preference on how the home initialization will be done. Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: default config machinery
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- . 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
Re: default config machinery
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
On Monday 16 April 2012, Lamarque V. Souza wrote: > As long as the renaming is atomic then yes. Remember the plasma- > mobile/plasma-device renaming? It is still half made and causes > inconsistency. Is it possible to rename a repo without recreating it? I > can use that in another project if it is simple. > > Is there are need for that repo now? Shouldn't its contents be part of > plasma-mobile-config and plasma-contour-config deleted? is using the plasma-mobile-config git repo, just maintained the old package name for now > > * plasma-contour-config also provides the startactive-modules package > > (would go away from the startactive package, would make sense to not > > provide any module in the startactive repo?) > > If you remove the configuration from the startactive repo add a > readme.txt indicating where to look for the configuration files. More and > more people are trying to build Plasma Active packages by theirselves and > having software in one repo/package and their configuration in other > repo/package make things a bit more complicated to get up and running. > Sometimes you think the software is not working but it just lacks the > configuration because nowhere in the repo indicates how to configure them > properly. yeah, i'm not sure what is the best way to go here: keeping in the startactive repo (so branching that if needed) or move everything > > * contour-intro only contains demo data (images, video) > > > > * the package kde-skel-binary has the nepomuk database dump, the idea is > > to import it with the /etc/skel mechanism > > Why the binary suffix? I know the database is a binary file, but what > adds to the fact the package contains the skeleton of an user account? the idea was to separate if will be needed one with text config files as well, but since we may get away to use global config files for everything default it may be not necessary so -binary may be dropped -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: default config machinery
Em Monday 16 April 2012, Marco Martin escreveu: > Hi all, Hi, > 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 use it, i've attempted the following: > * did a branch of the devel repo in my home > > https://build.pub.meego.com/project/packages?project=home%3Amart%3Abranche > s%3AProject%3AKDE%3ADevel > > * it has plasma-contour-config using the new git repo (maybe a rename is > worth?) As long as the renaming is atomic then yes. Remember the plasma- mobile/plasma-device renaming? It is still half made and causes inconsistency. Is it possible to rename a repo without recreating it? I can use that in another project if it is simple. Is there are need for that repo now? Shouldn't its contents be part of plasma-mobile-config and plasma-contour-config deleted? > * plasma-contour-config also provides the startactive-modules package > (would go away from the startactive package, would make sense to not > provide any module in the startactive repo?) If you remove the configuration from the startactive repo add a readme.txt indicating where to look for the configuration files. More and more people are trying to build Plasma Active packages by theirselves and having software in one repo/package and their configuration in other repo/package make things a bit more complicated to get up and running. Sometimes you think the software is not working but it just lacks the configuration because nowhere in the repo indicates how to configure them properly. > * contour-intro only contains demo data (images, video) > > * the package kde-skel-binary has the nepomuk database dump, the idea is to > import it with the /etc/skel mechanism Why the binary suffix? I know the database is a binary file, but what adds to the fact the package contains the skeleton of an user account? -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
default config machinery
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 use it, i've attempted the following: * did a branch of the devel repo in my home https://build.pub.meego.com/project/packages?project=home%3Amart%3Abranches%3AProject%3AKDE%3ADevel * it has plasma-contour-config using the new git repo (maybe a rename is worth?) * plasma-contour-config also provides the startactive-modules package (would go away from the startactive package, would make sense to not provide any module in the startactive repo?) * contour-intro only contains demo data (images, video) * the package kde-skel-binary has the nepomuk database dump, the idea is to import it with the /etc/skel mechanism any test and/or comment is appreciated :D Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
