ok, does anybody mind if i disable bittorrent support in KGet sources
for Applications/16.04 and master (still qt4-based) branches?
> > FWIW, the library not being co-installable is kind of a bug, or at
> > least bad form anyway.
>
> That is true, of course.
> The two things are probably orthogon
distro packagers note that libktorrent for kf5 conflicts with the one for kde4,
which is needed for kget.
kget for kf5 is in a semi-ported state now, and i wonder if anyone uses it at
all. for example it has konqueror integration, but hey who uses konqueror
nowadays? chromium, firefox and qupzi
> Nick, what did you use for KTorrent?
i used kde-dev-scripts, with the patch attached to this mail.
export XZ_OPT=-9
./create_tarball.rb -v 2.0.1 -n -a libktorrent
./create_tarball.rb -v 5.0.1 -n -a ktorrent
the script retrieves sources from trunk/master, but this was fine for me
because i didn
Hi. Can somebody point me to the script that gathers .po files of an extragear
app
and creates a release tarball?
i tried create_tarball.rb from kde-dev-scripts, but it tries to download
ktorrent sources from svn.
Hi! I have finished porting KTorrent to KF5 some time ago and now I believe
that it is ready to be released.
But pushing 5.0 branch is denied by git server. Current KTorrent maintainer is
not active for few years already.
Whom should i ask to get the permissions necessary for creating new branch
> To be honest, I've tried to use it many times, but I always seem to
> end up diving in warnings in other projects. It's hard to filter for
> projects I have a grasp on.
>
> How do you deal with this?
i just sort by filepath/name (the column is on the right, you need to scroll
horizontally to g
> > Let us know in this thread if code you're interested in isn't there.
> Could we have kdegames there?
ok, i'll include them in the next build (in a week or so)
--- Исходное сообщение ---
От кого: "Vishesh Handa"
Дата: 26 ноября 2014, 18:11:13
>
> Hey Nick
>
>
> I noticed that you ported the po extractor of Strigi to KFileMetadata.
> However, you didn't go through review or actually discuss this change
> anywhere, which is quite sad.
>
>
