Package Details: targetcli-fb 2.1.58-1

Git Clone URL: https://aur.archlinux.org/targetcli-fb.git (read-only, click to copy)
Package Base: targetcli-fb
Description: free branch of the targetcli LIO administration shell (iSCSI + Co)
Upstream URL: https://github.com/open-iscsi/targetcli-fb
Licenses: Apache
Provides: targetcli
Submitter: JonnyJD
Maintainer: dsonck92
Last Packager: dsonck92
Votes: 24
Popularity: 0.92
First Submitted: 2012-02-27 01:05 (UTC)
Last Updated: 2024-06-09 12:32 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

JonnyJD commented on 2013-07-25 08:49 (UTC)

Please note that the license changed from AGPL3 to Apache 2.0 with fb27.

JonnyJD commented on 2013-04-08 10:20 (UTC)

There was a change in targetcli-fb to only show the backends you have the hardware available for: https://github.com/agrover/targetcli-fb/commit/e302e0b781a38d852d89e4faf3a29689b10f5f0d So you might be looking at the wrong place to check general support or targetcli-fb can't find your hardware. These targets were not removed from the code: https://github.com/agrover/rtslib-fb/blob/master/rtslib/fabric.py#L483 The difference between targetcli and targetcli-fb is that there is not much of development and no community for targetcli, but there are lots of changes and some community patches for targetcli-fb (free branch). Have a look at https://github.com/agrover/targetcli-fb/network The "upstream" branch is targetcli. "master" is targetcli-fb. Risingtidesystems have a commercial product (rtsadmin) and are probably mainly working on that. Targetcli is open source, but not a community project.

quartz64 commented on 2013-04-08 09:55 (UTC)

What is the main difference between targetcli-fb and targetcli? I've noticed that there is no FC target (qla2xxx) and FCoE target (tcm_fc) in targetcli-fb.

TheImperial2004 commented on 2013-04-05 20:13 (UTC)

I edited all the files manually since I had free time . I'm not in an urgent need for a -git package now . Thanks .

TheImperial2004 commented on 2013-04-05 18:16 (UTC)

Oops ! I used the wrong words .. What I meant was exactly what you explained . Every time I update the package using yaourt , it checks the git repo and compile from there . Currently I reformated the server because of an RC kernel issues (noob) , and I would really use a -git package of RTSlib-fb + Targetcli-fb as editing those files manually would take alot of time . Of course if you have the time . Thank you , really appreciated .

JonnyJD commented on 2013-04-05 17:42 (UTC)

That is not how it works. -git packages are updated every time they are built. So the PKGBUILD doesn't change in the AUR, but "makepkg" will check for the current commit and update the pkgver with the current date. So it would be up to you to build targetcli-fb-git/rtslib everytime you need it or automatically (I wouldn't suggest that. It can break things unexpectedly) You can also create a "-local" package that basically just creates symlinks to a folder on your machine, which again is a repository, which again gets a "git pull" with cron. I can't create that in the AUR, since it does depend on your local machine. Have a look at this example though: https://gist.github.com/JonnyJD/5321159 (another package, but this is how it works) There will be a new targetcli/rtslib release "early this coming week". I'd recommend to stick to that. You do have a running build now after updating some files manually once, right? Ping me again if you would still use a -git. I will create one then.

TheImperial2004 commented on 2013-04-05 15:50 (UTC)

Yes , if a -git package is going to be updated automatically as new commits get pushed into the repo . Thanks !

JonnyJD commented on 2013-04-05 10:28 (UTC)

Hm, I followed that ticket, but there is no new release yet and I can't find that one commit (or 2) I could use as a patch without breaking other things. I could create -git packages for rtslib and targetcli. Would that help?

TheImperial2004 commented on 2013-04-05 09:16 (UTC)

Can you update the package please ? The GitHub repo contains an important ib_srpt bug fix now . thank you .

JonnyJD commented on 2013-02-18 00:11 (UTC)

I included the systemd file from fedora, which works fine. The old sysvinit file is still provided for now, but will go away in a couple of releases. I also explicitely added the free branch of configshell to make automatic install easier without pulling epydoc. Feel free to uninstall epydoc and dependencies now.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »